Use new lazy serialization in FIRRTL #2741
Merged
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.
This enables emission of modules that serialize to >2 GiB of .fir text.
See chipsalliance/firrtl#2554.
This has no impact on performance for most designs, it slightly improves serialization performance for designs with very large modules (due to the cost of allocating large Strings--but the JVM is very good at this so the impact is small).
Contributor Checklist
docs/src
?Type of Improvement
API Impact
No change
Backend Code Generation Impact
No impact
Desired Merge Strategy
Release Notes
Support serialization of Modules that require over 2 GiB of
.fir
text.Reviewer Checklist (only modified by reviewer)
3.4.x
, [small] API extension:3.5.x
, API modification or big change:3.6.0
)?Enable auto-merge (squash)
, clean up the commit message, and label withPlease Merge
.Create a merge commit
.