Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Event persistence within a time slot

Hardware interview practice

Event persistence within a time slot

MediumVerification UtilitiesSystemVerilog

Why can wait(e.triggered) be safer than @e for synchronization among processes active in the same time slot?

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 →
Starting point

Question code

event e;
// one process triggers e; another tests e.triggered
Choose one

Answer choices

  1. A. triggered remains true forever after the first trigger
  2. B. triggered remains true for the remainder of the current time step, so a same-slot waiter need not miss an earlier trigger
  3. C. @e is illegal in a class method
  4. D. wait(e.triggered) schedules the trigger automatically
Continue practicing

Related questions

Verification UtilitiesBounded mailboxes→
asic.fyi · Learn silicon end to end.info@asic.fyi