In reply to dave_59:
In reply to drogoff:
The warning you are getting is from the compiler before the
is_active flag gets set during simulation. When it comes to procedural code the compiler does not know what source code will or will not get executed. It has to generate the machine code to execute everything.
without seeing the actual code, the only thing I can suggest to change the code to make it work in for any setting of
is_active. That might mean changing the interface signal to a wire.
Yep - that was it. This also explains why I see examples of SV Interfaces with the signals declared as wires and not logic. I couldn’t figure out why this was being done since, with modports, no signal was bidirectional or multiply driven. Now it makes sense although it’s a bit ugly.
Thanks!
David