Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

_Py_NO_SANITIZE_UNDEFINED is defined twice when compiling with recent GCC #129838

Closed
Labels
buildThe build process and cross-buildextension-modulesC modules in the Modules dirtype-bugAn unexpected behavior, bug, or error
@collinfunk

Description

@collinfunk

Bug report

Bug description:

When compiling with a recent version of GCC and enabling undefined sanitizer, I see the following warning:

./Modules/faulthandler.c:49:11: warning: "_Py_NO_SANITIZE_UNDEFINED" redefined   49 | #  define _Py_NO_SANITIZE_UNDEFINED __attribute__((no_sanitize_undefined))      |           ^~~~~~~~~~~~~~~~~~~~~~~~~./Modules/faulthandler.c:44:13: note: this is the location of the previous definition   44 | #    define _Py_NO_SANITIZE_UNDEFINED __attribute__((no_sanitize("undefined")))      |             ^~~~~~~~~~~~~~~~~~~~~~~~~

The conditions just need some updating to match recent GCC and Clang versions.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildThe build process and cross-buildextension-modulesC modules in the Modules dirtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp