Repository navigation
Conversation
djolertrk
added this pull request to stack #6
October 5, 2026 08:19
Collaborator
Author
|
cc @cameel |
djolertrk
force-pushed
the
feature/ethdebug-yul-side-table
branch
from
October 8, 2026 13:47
7f09c73 to
ca84699
Compare
djolertrk
force-pushed
the
feature/ethdebug-yul-side-table
branch
from
October 9, 2026 10:51
ca84699 to
7d89200
Compare
djolertrk
force-pushed
the
feature/ethdebug-yul-side-table
branch
from
October 9, 2026 12:45
7d89200 to
f82d0f4
Compare
djolertrk
force-pushed
the
feature/ethdebug-yul-side-table
branch
from
October 16, 2026 12:00
f82d0f4 to
af85835
Compare
…t round trip Attach the scope records of the side table to Yul AST nodes through DebugData, keyed by (AST ID, instance), and keep them across the Yul -> text -> Yul reparse the compiler performs after optimization: records are collected from the AST into the retained table before printing and reattached by their @ast-id annotations after parsing. Attaching re-checks every pointer against the current code: a materialized variable (or update) whose pointer reads a generated Yul local that no longer exists becomes optimized-out instead of keeping a stale pointer. The check is scoped per object. Scope instances travel in the new @ast-id-instance annotation next to @ast-id, so passes that clone code can give each copy its own records; code generation only produces instance 0. Contract-level scopes attach to the top-level block of each object, which now carries the contract's AST ID. Blocks generated by the function grouper and hoister keep locations only, so they do not inherit another node's identity. CompilerStack stores the attached table on the contract; it pairs with the unoptimized IR, whose generated locals it references. The golden tests now show Contract.semantic as attached.
djolertrk
force-pushed
the
feature/ethdebug-yul-side-table
branch
from
October 19, 2026 15:28
af85835 to
664ca54
Compare
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
1 participant
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.
Attach the scope records of the side table to Yul AST nodes through DebugData, keyed by (AST ID, instance), and keep them across the Yul -> text -> Yul reparse the compiler performs after optimization: records are collected from the AST into the retained table before printing and reattached by their @ast-id annotations after parsing.
Attaching re-checks every pointer against the current code: a materialized variable (or update) whose pointer reads a generated Yul local that no longer exists becomes optimized-out instead of keeping a stale pointer. The check is scoped per object.
Scope instances travel in the new @ast-id-instance annotation next to @ast-id, so passes that clone code can give each copy its own records; code generation only produces instance 0. Contract-level scopes attach to the top-level block of each object, which now carries the contract's AST ID. Blocks generated by the function grouper and hoister keep locations only, so they do not inherit another node's identity.
CompilerStack stores the attached table on the contract; it pairs with the unoptimized IR, whose generated locals it references. The golden tests now show Contract.semantic as attached.