GH-100982: Break up COMPARE_AND_BRANCH#102801
Merged
Uh oh!
There was an error while loading. Please reload this page.
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.
COMPARE_AND_BRANCH(and its specializations) are a bit weird. It's basically an "adaptive superinstruction" that's present inco_code, and its semantics and lifecycle are different from that of any other instruction. Not only can it be harder to reason about, but it also makes changes (like quickening in the compiler) more awkward.However, it appears to be only a small improvement over
COMPARE_OP. This branch replaces theCOMPARE_AND_BRANCHfamily with a "normal"COMPARE_OPone; here are some microbenchmarks for specializations with and without conditional jumps (non-debug, non-PGO):main:This branch:
So
COMPARE_AND_BRANCHonly gets us a <1ns improvement in the (common) branching case, and it costs us about 2-4ns in the (uncommon) non-branching case. Honestly, I don't think that's enough of a win.(Benchmarks are slightly slower, but in the noise.)