Hardware interview practice
Event persistence within a time slot
Why can wait(e.triggered) be safer than @e for synchronization among processes active in the same time slot?
Starting point
Question code
event e;
// one process triggers e; another tests e.triggeredChoose one
Answer choices
- A. triggered remains true forever after the first trigger
- B. triggered remains true for the remainder of the current time step, so a same-slot waiter need not miss an earlier trigger
- C. @e is illegal in a class method
- D. wait(e.triggered) schedules the trigger automatically
