-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
gh-133171: Re-enable JUMP_BACKWARD to free-threading build #137800
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
base: main
Are you sure you want to change the base?
Conversation
@savannahostrowski @diegorusso @Fidget-Spinner @brandtbucher To the JIT team — I’m not sure who’s currently working on this, but it might be a good starting point to add JIT support. My next goal will be to make the tier-two instructions thread-safe. |
I think we should start by running the tests in CI for JIT+FT current build and see what passes/fails before doing this |
We disabled FT + JIT build from #133179 do you think that we have to listing the current status? |
This makes sense but actually the default build's JIT can't even run with the optimizer turned off! There's some segfaults when we turn off the optimizer lol. |
How can I trigger this? |
Run the test suite with |
Just for the record at default build:
|
This comment has been minimized.
This comment has been minimized.
Ah never mind, it need to be transformed tier 2 code first. |
Uh oh!
There was an error while loading. Please reload this page.