-
Notifications
You must be signed in to change notification settings - Fork 277
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
[SVExtractTestCode] Instance inlining doesn't update inner symbols and clone sv.bind #5665
Labels
Comments
Another example
|
uenoku
added a commit
that referenced
this issue
Jul 26, 2023
…ner symbols and clone sv.bind Close #5665. This commit fixes a bug that bound instances are accidentally erased. When inlining input only modules it's necessary to clone bind statements for bound instances in the module. Previously single bind op is shared by multiple instances, as a result ExportVerilog only emits a bind statement for one of them.
uenoku
added a commit
that referenced
this issue
Jul 26, 2023
…nner symbols and clone sv.bind (#5679) Close #5665. This commit fixes a bug that bound instances are accidentally erased. When inlining input only modules it's necessary to clone bind statements for bound instances in the module. Previously single bind op is shared by multiple instances, as a result ExportVerilog only emits a bind statement for one of them.
uenoku
added a commit
that referenced
this issue
Jul 31, 2023
…nner symbols and clone sv.bind (#5679) Close #5665. This commit fixes a bug that bound instances are accidentally erased. When inlining input only modules it's necessary to clone bind statements for bound instances in the module. Previously single bind op is shared by multiple instances, as a result ExportVerilog only emits a bind statement for one of them.
uenoku
added a commit
that referenced
this issue
Aug 2, 2023
…nner symbols and clone sv.bind (#5679) Close #5665. This commit fixes a bug that bound instances are accidentally erased. When inlining input only modules it's necessary to clone bind statements for bound instances in the module. Previously single bind op is shared by multiple instances, as a result ExportVerilog only emits a bind statement for one of them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current output with
firtool -extract-test-code
.The second assertion is not emitted in the bind file. This is because bind op is not cloned properly when input only modules are inlined and the first instance (in the instance graph ndoe iterator) is preserved. This bug was first introduced by 0d5cf22 which was included in 1.17.0.
The text was updated successfully, but these errors were encountered: