Skip to content
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

No inlining let-bound global vars with clock types (copy #2846) #2853

Merged
merged 1 commit into from
Dec 7, 2024

Conversation

DigitalBrains1
Copy link
Member

The global vars are usually backed by a clock generator that are not work-free.

In addition, when these global vars are recursively defined, they can mess up the post-normalization flattening stage which then violates certain invariants of the netlist generation stage. This then causes the netlist generation stage to generate bad Verilog names.

Fixes #2845

This is a backport of #2846. The PR on master was malformed somehow, with the correct contents but missing the commit message above and an incorrect Git structure. This backport to 1.8 is reconstructed by hand.

The global vars are usually backed by a clock generator that
are not work-free.

In addition, when these global vars are recursively defined,
they can mess up the post-normalization flattening stage which
then violates certain invariants of the netlist generation stage.
This then causes the netlist generation stage to generate bad
Verilog names.

Fixes #2845

(The PR on master was malformed somehow, with the correct contents but
missing the commit message above and an incorrect Git structure. This
backport to 1.8 is reconstructed by hand.)
Copy link
Member

@christiaanb christiaanb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@DigitalBrains1 DigitalBrains1 enabled auto-merge (squash) December 7, 2024 14:17
@DigitalBrains1 DigitalBrains1 merged commit 0950423 into 1.8 Dec 7, 2024
17 checks passed
@DigitalBrains1 DigitalBrains1 deleted the backport-2846 branch December 7, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants