-
-
Notifications
You must be signed in to change notification settings - Fork 34.4k
CYGWIN: GCC prints "defined but not used" warnings on mimalloc #146594
Copy link
Copy link
Open
Labels
OS-windowsbuildThe build process and cross-buildThe build process and cross-builddependenciesPull requests that update a dependency filePull requests that update a dependency fileinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)triagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Metadata
Metadata
Assignees
Labels
OS-windowsbuildThe build process and cross-buildThe build process and cross-builddependenciesPull requests that update a dependency filePull requests that update a dependency fileinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)triagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
Compiling under CYGWIN prints these warning messages:
Looking into the code of
Objects/mimalloc/prim/unix/prim.c, there is already a conditional block to avoid the generation of such warnings.The solution for this issue is to simply add CYGWIN to that list of platforms.
So, I'm posting this issue according to the suggestion received into #146572 for tracking this change.
CPython versions tested on:
CPython main branch
Operating systems tested on:
Windows
Linked PRs