perf: box Variable.info, BlockEnd::Match, and Statement::EnumConstruct#9841
Draft
eytan-starkware wants to merge 1 commit intomainfrom
Draft
Conversation
Box three large/rare lowering IR fields to reduce container sizes:
- Variable.info: TypeInfo (~160 bytes) → Box<TypeInfo> (8 bytes inline)
- BlockEnd::Match { info }: MatchInfo → Box<MatchInfo>
- Statement::EnumConstruct: StatementEnumConstruct → Box<...>
Empirically selected from testing all 5 candidates individually and in
combinations. This 3-combo gives the best ERC20 Starknet results:
-2.8% total allocations, -2.3% peak memory. fib.cairo is neutral.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
This change is |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
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
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.
Summary
Type of change
Please check one:
Why is this change needed?
What was the behavior or documentation before?
What is the behavior or documentation after?
Related issue or discussion (if any)
Additional context