-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unused signal seems not to change #245
Comments
Yes. The RTLIL backend has intentionally never made any guarantees about the behavior of unused signals. But maybe that should be changed. |
Actually, this case is a bit special: the signal is both read and written, so it's not really unused (it depends on itself). I am not sure why this happens. |
I believe this is not an nMigen issue. As you can see, the RTLIL it emits contains your signal (edited for clarity):
Can you please confirm, and raise the issue upstream? |
Submitted yosys issue 1441 |
Thanks. Closing as purely an upstream issue; will reopen if it turns out nMigen is involved. |
Versions:
In this file, the signal
unf
is required to toggle on the negative clock, but doesn't, unless it is listed in the ports when callingmain
.test_case.py
:test_case.sby
:Running:
When
unf
is not in the list of ports:When
unf
is in the list of ports:This is very inconvenient, especially when you get down multiple levels of modules and some of the signals in the modules are for testing purposes, and need to be seen without having to port them out.
The text was updated successfully, but these errors were encountered: