NotificationsYou must be signed in to change notification settings
Fork32k
Star67.2k

[3.13] gh-129838: Don't redefine _Py_NO_SANITIZE_UNDEFINED (GH-129839)#130366

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

vstinner merged 1 commit intopython:3.13frommiss-islington:backport-568db40-3.13

Feb 20, 2025

Merged

[3.13] gh-129838: Don't redefine _Py_NO_SANITIZE_UNDEFINED (GH-129839)#130366

vstinner merged 1 commit intopython:3.13frommiss-islington:backport-568db40-3.13

Feb 20, 2025

Conversation

Copy link

Contributor

miss-islington commentedFeb 20, 2025•
edited by bedevere-appbot
Loading

Newer GCC versions accept bothattribute((no_sanitize("undefined")))
andattribute((no_sanitize_undefined)) so check that the macro is
not already defined.
(cherry picked from commit568db40)

Co-authored-by: Collin Funkcollin.funk1@gmail.com

Issue:_Py_NO_SANITIZE_UNDEFINED is defined twice when compiling with recent GCC #129838

pythongh-129838: Don't redefine _Py_NO_SANITIZE_UNDEFINED (pythonGH-1…

364ade4

…29839)Newer GCC versions accept both __attribute__((no_sanitize("undefined")))and __attribute__((no_sanitize_undefined)) so check that the macro isnot already defined.(cherry picked from commit568db40)Co-authored-by: Collin Funk <collin.funk1@gmail.com>