-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
gh-130039: Tailcall for windows builds #130040
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
Changes from 15 commits
ab0a611
d57c175
3eb568f
4dd19cf
7f91920
c3d656b
3638cda
b8b79ed
d3766d8
c811b8a
904b7ee
991b50f
166187c
5f7ad24
6d7b689
aadfec4
1d7c051
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 commentThe 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 commentThe 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. |
||
#define _GENERATE_DEBUG_SECTION_WINDOWS(name) \ | ||
_Pragma(Py_STRINGIFY(section(Py_STRINGIFY(name), read, write))) \ | ||
__declspec(allocate(Py_STRINGIFY(name))) | ||
|
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.)
(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