-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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-130039: Tailcall for windows builds #130040
base: main
Are you sure you want to change the base?
Conversation
Fidget-Spinner
commented
Feb 12, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: Tail calling interpreter for Windows #130039
@mdboom I'm baffled by the error in the CI. By any chance do you know how to fix it? https://github.com/python/cpython/actions/runs/13287244377/job/37098802007?pr=130040 |
I can try poking at this locally a bit later today, but my first guess is that it's because the equals sign is getting swallowed here:
...so I don't really understand the quoting rules for PowerShell -- maybe I think I ran into this same problem in bench-runner, and I ultimately gave up and used |
That makes sense. Thanks. Applied the change to use cmd instead! |
@chris-eibl I guess we're blocked on getting patches to make |
Nevermind, I will try to patch them into this PR as well, so that we can do an integration test. |
Yeah, see this part of
Had a quick look at the PR and everything looks fine to me. The build log of your latest commit 7f91920 shows
I have never seen that error before. For sure not during assembling, must come out of _asynciomodule.c:
That's the only occurence I've found. Ah - you've found it yourself while I was typing :) Interestingly: I cannot reproduce locally for the failing commit 7f91920 using:
with Visual Studio 2022 17.13.0 Preview 5.0, which ships with cl.exe 19.43.34808 and clang 19.1.1. Let's see whether your latest commit fixes CI - looks promising :) |
I'm pretty sure this advice assumes using cmd, not PowerShell (which is the default on Github Actions). Overriding the shell used on Github Actions seems to be the easy solution. The harder solution is figuring out PowerShell's escaping rules... |
That didn't fix it :(. |
Ups - still the same error - very weird. No idea atm - sorry ... |
Unfortunately I cannot reproduce locally. Have a different clang version, though. Did also use clang 19.1.6 a lot. Will fire up a build for this commit ... Update:
|
Ah.. I think I forgot to add parentheses :) my bad |
Nevermind, that didn't fix it. Now that I look at the macros closer, it shouldn't fix it either. |
Really strange why that happens on CI. Cannot reproduce with clang 19.1.1 and 19.1.6. Those macros have been touched recently #129223. |
Fixed it on CI! |
.github/workflows/tail-call.yml
Outdated
choco install llvm --allow-downgrade --no-progress --version ${{ matrix.llvm }}.1.0 | ||
./PCbuild/build.bat --tail-call-interp -d -p ${{ matrix.architecture }} | ||
choco install llvm --allow-downgrade --no-progress --version ${{ matrix.llvm }}.1.5 | ||
./PCbuild/build.bat --tail-call-interp -d -p ${{ matrix.architecture }} "/p:PlatformToolset=clangcl" "/p:LLVMToolsVersion=19.1.5" "/p:LLVMInstallDir=C:\Program Files\LLVM" |
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.
It might be convenient to add --clang
as a build.bat option, though you'd still need the quoting to get the other variables in.
Also, FWIW, unless you're explicitly trying to override other settings, you can set these variables as environment variables instead. The MSBuild files can override those if it isn't authored properly, but at least PlatformToolset
is correct, and I expect the other two will be too.
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.
Actually, I was thinking of using the default clang that comes with VS. The latest VS comes with Clang 19, so it's perfect for this. However, I don't know if the CI runners updated to use the latest VS yet, and I don't want a situation where sometimes we break on older VS and sometimes we don't. So for now, I'll let users manually specify, and maybe in a year or so we can revisit adding a --clang
option.
@zooba gentle ping for a review please. Thanks again for reviewing that other PR on getting PGO working on clang-cl. This should be relatively tame in comparison :). |
Co-authored-by: Hugo van Kemenade <[email protected]>
@@ -23,7 +23,7 @@ extern "C" { | |||
declaration \ | |||
_GENERATE_DEBUG_SECTION_LINUX(name) | |||
|
|||
#if defined(MS_WINDOWS) | |||
#if defined(MS_WINDOWS) && !defined(__clang__) |
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.
Does this need an alternate definition for Windows + clang?
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.
No, below there's a default that it uses is we're not one of the supported platforms. And that default works for Clang Windows.
.github/workflows/tail-call.yml
Outdated
@@ -2,12 +2,14 @@ name: Tail calling interpreter | |||
on: | |||
pull_request: | |||
paths: | |||
- '.github/workflows/tail-call.yml' |
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.
This feels wrong to me, but if it's needed, then sure. Hopefully someone else can sign off on this part of the change.
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.
This is fine: when changing this file, it's good to run it as well to make sure we didn't break it -- which is rather too easy with YAML.
(And let's strip the trailing spaces.)
- '.github/workflows/tail-call.yml' | |
- '.github/workflows/tail-call.yml' |
(We should add yaml
to this list, feel free to include it in the PR if you like:)
cpython/.pre-commit-config.yaml
Line 49 in 2904ec2
types_or: [c, inc, python, rst] |
We can't specify the minor version as the apt script doesn't recognize it.
Looks fine to me. I hope we can justify (one day) taking options out of |