MAINT: Fix for segfaults with GCC 15 #29134
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
GCC 15 generates code that segfaults on newer hardware when running tests. See numpygh-28991 for details. A fix is to always require alignment, which can be done by setting `NPY_ALIGNMENT_REQUIRED = 1`. We completely remove `NPY_ALIGNMENT_REQUIRED` here in order to test downstream compatibility before the 2.4 release. It is not expected to cause problems, but one never knows. The associated macro `NPY_USE_UNALIGNED_ACCESS` could also be removed as it is always 0, but that is left for another PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GCC 15 generates code that segfaults on newer hardware when running tests. See gh-28991 for details. A fix is to always require alignment, which can be done by setting
NPY_ALIGNMENT_REQUIRED = 1.We completely remove
NPY_ALIGNMENT_REQUIREDhere in order to test downstream compatibility before the 2.4 release. It is not expected to cause problems, but one never knows. The associated macroNPY_USE_UNALIGNED_ACCESScould also be removed as it is always 0, but that is left for another PR.Closes #28991.