Skip to content
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

x86jit: Correct jitbase range comparison #18080

Merged
merged 1 commit into from Sep 6, 2023

Conversation

unknownbrackets
Copy link
Collaborator

This was wrong for checking jitbase was negative, although that probably never happens within actually 64-bit pointers. Still, fixes a warning and code looked wrong - meant to take out the Us.

-[Unknown]

@unknownbrackets unknownbrackets added the x86jit x86/x64 JIT bugs label Sep 6, 2023
@unknownbrackets unknownbrackets added this to the v1.16.0 milestone Sep 6, 2023
@hrydgard hrydgard merged commit f2512e0 into hrydgard:master Sep 6, 2023
18 checks passed
@unknownbrackets unknownbrackets deleted the x86jit-minor branch September 6, 2023 07:26
@fp64
Copy link
Contributor

fp64 commented Sep 6, 2023

You took out a zero instead of U here:

if (jitbase < -0x8000000ULL || jitbase > 0x7FFFFFFFLL) {

@hrydgard
Copy link
Owner

hrydgard commented Sep 6, 2023

I'll push a fix for that, should have seen it, heh.

hrydgard added a commit that referenced this pull request Sep 6, 2023
@fp64
Copy link
Contributor

fp64 commented Sep 6, 2023

It's amusing how normally ull is more legible than ULL, but LL is more legible than ll (assuming all-uppercase hex digits, anyway).

@unknownbrackets
Copy link
Collaborator Author

Arg, sorry.

-[Unknown]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
x86jit x86/x64 JIT bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants