-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
GH-100982: Break up COMPARE_AND_BRANCH
#102801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH-100982: Break up COMPARE_AND_BRANCH
#102801
Conversation
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.
Looks good.
Sorry, something went wrong.
All reactions
markshannon
iritkatriel
Successfully merging this pull request may close these issues.
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_BRANCH
family with a "normal"COMPARE_OP
one; here are some microbenchmarks for specializations with and without conditional jumps (non-debug, non-PGO):main
:This branch:
So
COMPARE_AND_BRANCH
only 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.)