You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases it is desirable to create a signal with a name that doesn't show up in the waveform viewer, such as when a signal is created to hold the results of intermediate computations, or to change shape, and it would just add noise. I propose adding a notion of a "private signal name".
I suggest changing naming rules so that Signal(name="") creates a signal with a private name. Such a signal is translated to a private wire in RTLIL (with a $\d+ name), doesn't get displayed in the waveform viewer, and so on.
The FSM ongoing signals (not the state signal) should be changed to have private names in the 0.5 milestone.
The text was updated successfully, but these errors were encountered:
In some cases it is desirable to create a signal with a name that doesn't show up in the waveform viewer, such as when a signal is created to hold the results of intermediate computations, or to change shape, and it would just add noise. I propose adding a notion of a "private signal name".
I suggest changing naming rules so that
Signal(name="")
creates a signal with a private name. Such a signal is translated to a private wire in RTLIL (with a$\d+
name), doesn't get displayed in the waveform viewer, and so on.The FSM ongoing signals (not the state signal) should be changed to have private names in the 0.5 milestone.
The text was updated successfully, but these errors were encountered: