-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vcd file includes blank traces #91
Comments
Which signal in the trace above are you referencing? f_counter1? or some other signal? |
Yes
…On Fri, 12 Jun 2020, 22:53 Dan Gisselquist, ***@***.***> wrote:
Which signal in the trace above are you referencing? f_counter1? or some
other signal?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE223DDCRBX2BJTTW2IE33RWKITFANCNFSM4N4HAERA>
.
|
I'm confused then. |
f_counter1 shows in the trace but there is no data. It is incrementing every time like f_counter2. Previously I've noticed that signals that are not used in the formal process are not present in the vcd (unless using keep). The above is an example of an unused signal trace being kept but containing no data. |
Ok, I see it now, it's not that Yeah, that looks like a bug. Dan |
It's the call to If you just want |
Here's an ugly hotfix for if you want proper traces:
This sets the |
I recall previous behaviour was that untouched signals were dropped from the vcd. Now untouched signals are present in the vcd but have no value - which IMO is more confusing.
counter.zip
The text was updated successfully, but these errors were encountered: