4095af5fd6
Fix the drain functionality of the RubyPort to only call drain on child ports during a system-wide drain process, instead of calling each time that a ruby_hit_callback is executed. This fixes the issue of the RubyPort ports being reawakened during the drain simulation, possibly with work they didn't previously have to complete. If they have new work, they may call process on the drain event that they had not registered work for, causing an assertion failure when completing the drain event. Also, in RubyPort, set the drainEvent to NULL when there are no events to be drained. If not set to NULL, the drain loop can result in stale drainEvents used. |
||
---|---|---|
.. | ||
buffers | ||
common | ||
filters | ||
network | ||
profiler | ||
recorder | ||
slicc_interface | ||
system | ||
SConscript | ||
SConsopts |