Support residual codegen data in pipelines #3126
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added test. Minor fix.
meheff
force-pushed
the
meheff/2025-09-26-residual-data-pipeline
branch
from
66327df to
68fa805
Compare
richmckeever
approved these changes
Sep 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Residual codegen data includes metadata about the codegen process. It can be consumed in a later codegen invocation to minimize the differences in the generated verilog. Previously only the combinational generator was supported. This change adds support for the pipeline generator.
Ideally the schedule would be similarly handled to minimize schedule changes, but this change is a step toward full support in the pipeline generator.