Simulation performance improvements for conditional assignments

[mkorbel1]

Description & Motivation

Benchmarking, profiling, and usage of recent changes in other designs revealed a few small optimizations that could be made to improve simulation performance when many conditional assignments are used.

• WriteAfterReadException no longer prints the signal name. This enables creating one single static function for all write-after-read violations rather than creating a new one during simulation for each signal guarded. The loss in debug visibility is minimal since signal names going into a Conditional are already often not well-named signals, and the full stack trace can provide much more detail.
• Looking up the receiver on each execution of ConditionalAssign was redundant overhead, so caching it saves some performance.

Related Issue(s)

N/A

Testing

Existing tests cover functionality. CombGuardFanoutBenchmark demonstrated some measurable performance improvements with these changes.

Backwards-compatibility

Is this a breaking change that will not be backwards-compatible? If yes, how so?

No

Documentation

Does the change require any updates to documentation? If so, where? Are they included?

No