This repository was archived by the owner on Aug 5, 2026. It is now read-only.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That causes the wrappers to be bigger and thus memory hoarding of already a heavy operation. Is that a huge problem for the debug setup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a large, measured problem: with -g, each probe variable's debug info pulls the complete DIE tree of its template argument (all member declarations, transitively) into the PTU — on our production replay (large-header trading workload, heavy
AppendTypesSlowtraffic) that was a 10x wall-clock regression, 1378s → 137s after suppressing, plus the DWARF itself hoarded per lookup. Against that, the attribute adds 26 bytes to a per-probe source buffer that already exists — paid on non-debug setups too, but it's noise next to the buffer itself. If even that bothers you I can gate the attribute text on whether the interpreter session has debug info enabled, at the cost of a slightly less uniform probe string.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, we can cheat on the JitCall side where just after we parse the prototype, we can check if we passed
-gto the interpreter, and then callsetAttr(createAttr(nodebug))on wrapper declaration. That would save bytes I believe.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No wait, on a second thought that might be suboptimal. Let's move forward with the current approach -- it would give us one more incentive to get rid of this string manipulations..