-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
Integration testing: Meson SIMD + vendored meson-python #24395
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Almost gives the same functionality as Distutils/CCompiler Opt, with a few changes to the way we specify the targets, also its abend idea of wrap the dispatchable sources, instead it counts on static libraries to enable different paths and flags.
Several renames have been made to certain compiler definitions that were used to determine the current target, as well as the macros in the dispatch configuration headers. These changes were necessary to allow for the modification of the prefix 'NPY_' in case this work is used outside of NumPy.
This simplifies the implementation and improves code readability.
Note that this is a bit messy. I tried to vendor spin's `meson.py` separately, but it's not possible to do so cleanly as far as I can tell. T 8000 he import machinery is unhappy bouncing around between `bin/spin`, `.spin/cmds.py and `.spin/meson.py`. So it was either folding the `spin/cmds/meson.py` content all into cmds.py, or vendor all of the spin package. This seems to work.
924294b
to
a594207
Compare
Finally Windows seems happy, builds are completing with the vendored meson/meson-python, and:
|
The failure on the Python 3.12 wheels is probably unrelated (and otherwise caused by the SIMD changes, not the build system ones):
Is this a known issue? |
rgommers
added a commit
to rgommers/numpy
that referenced
this pull request
Aug 11, 2023
Failed on Python 3.12 in numpygh-24395 testing. So this is an empty commit on top of `main` to check whether it's related to that PR. [skip azp] [skip circle] [skip cirrus] [skip travis]
rgommers
added a commit
to rgommers/numpy
that referenced
this pull request
Aug 11, 2023
Failed on Python 3.12 in numpygh-24395 testing. So this is an empty commit on top of `main` to check whether it's related to that PR. [skip azp] [skip circle] [skip cirrus] [skip travis]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not for merging! Testing the needed build system changes on top of gh-23096.