Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Reason about fork join_none and wait fork

Hardware interview practice

Reason about fork join_none and wait fork

EasySystemVerilogSystemVerilog

One parent process launches three child threads with fork...join_none and later executes wait fork. What happens?

Try it in the question bankReason first. Then compare.

Keep this exact question selected while you check your answer and review the full solution.

Practice this question →
Choose one

Answer choices

  1. A. The parent continues at join_none, then wait fork blocks until all outstanding children spawned by that parent finish.
  2. B. The parent blocks at join_none until one child finishes.
  3. C. join_none kills every child as soon as the parent reaches the next statement.
  4. D. The parent continues at join_none, then wait fork returns when the first child finishes.
asic.fyi · Learn silicon end to end.info@asic.fyi