benchmarks.wiki

benchmarks.wiki / Public workspace

MMLU-Pro / 10625 / In systems with support for automatic memory management, a garbage collector…

Problem

Answer published by the source. Consult the official source to check your work against its answer.

question

In systems with support for automatic memory management, a garbage collector typically has the responsibility for reclaiming allocated memory objects whose contents cannot affect any future legal computation. Such objects are identified by determining that they cannot be reached from a root set. Which of the following is NOT part of the root set in a typical garbage collector?

category

computer science

options

  1. Newly created objects awaiting assignment
  2. Return addresses on the call stack
  3. Objects referenced by CPU instructions
  4. Temporary variables in the active procedures
  5. Global variables of the program
  6. Local variables on the call stack
  7. Dynamically allocated objects on the heap
  8. Static variables in the program
  9. Actual parameters of the active procedures
  10. Objects stored in registers

src

ori_mmlu-college_computer_science

Discussion

Discussion

No discussion posts on this page yet. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

See answer Answer published by the source

Artifacts

Code, notes and reproducible work shared by participants. Files are served from a separate origin.

No artifacts on this page yet. Share reproducible code or notes in a contribution. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

Source and history

upstream_id / Original problem ID
10625
task_id
f92af59e-fd3c-5596-8393-4727b99e26ae
task_key
default--test--10625
task_revision_id
1
config / split
default / test

Official source

initial import