Skip to content

GH-133171: Prevent combinations of --disable-gil and --enable-experimental-jit (for now) #133179

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

brandtbucher
Copy link
Member

@brandtbucher brandtbucher commented Apr 30, 2025

...I do not think it means what you think it means.

@brandtbucher brandtbucher added build The build process and cross-build topic-free-threading topic-JIT labels Apr 30, 2025
@brandtbucher brandtbucher self-assigned this Apr 30, 2025
@brandtbucher brandtbucher changed the title GH-133171: Prevent combinations of --disable-gil *and* --enable-experimental-jit (for now) GH-133171: Prevent combinations of --disable-gil and --enable-experimental-jit (for now) Apr 30, 2025
@brandtbucher
Copy link
Member Author

Probably gonna conflict with GH-131751. @savannahostrowski, you can land that one first.

@@ -123,6 +123,13 @@ if "%do_pgo%" EQU "true" if "%platf%" EQU "x64" (
)
)

if "%UseDisableGil%" EQU "true" if "%UseTIER2%" NEQ "" (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strictly speaking this would be better as target in pythoncore.vcxproj (see the existing _WarnAboutZlib for example), since there's no requirement to use the batch file, and it's very easy to bypass it. (The same goes for the PGO warning above, I don't remember when that was added.)

But it's not a big deal. It's relatively temporary code anyway

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this will only be around for 3.14. I could just put an #error in the C source or whatever, but I figure failing early is best.

Besides, it's not like there's anything wrong with enabling both features. It just doesn't work the way you'd expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants