perf: Skip redundant stack limit analysis - #16902
Open
sbillig wants to merge 1 commit into
Open
Conversation
sbillig
force-pushed
the
perf/stacklimit-skip
branch
from
August 11, 2026 14:40
636ac4b to
ac71a09
Compare
sbillig
force-pushed
the
perf/stacklimit-skip
branch
from
August 13, 2026 02:35
ac71a09 to
7858cdc
Compare
sbillig
marked this pull request as ready for review
August 13, 2026 19:36
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
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.
Description
Skip running StackLimitEvader when StackCompressor determines that there are no stack-too-deep problems.
This avoids rebuilding the cfg, and repeating the same analysis.
It also avoids the rewriting of memoryguard literals from decimal to hex in the otherwise-noop case
that we now skip, hence the updated test output file changes. (Previously eg
memoryguard(128)would be rewritten tomemoryguard(0x80)unconditionally)On Uniswap v4-core, this reduces allocation calls by 19.085M (−3.2071%) and requested bytes by 3.396 GB (−3.7172%).