-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
Unreachable code warnings while building latest main at 48c70b8 #128086
Comments
I have updated the tcl-tk to version 9.0.0_1, the warnings are gone. Please refer - build.log |
I cannot reproduce this on my MacBook. The tcl-tk comment seems off-topic for this issue. Can you provide more information about your environment? |
Like gcc compiler version? and ...? |
Include everything that is needed to reproduce the failure you are seeing. Are you still seeing these failures? Did you compile from a clean source tree ( |
|
Still unable to reproduce. I'm on the same macOS version and the same compiler. |
Here is the |
Here is the make output i have capture with the command -
Main branch at b4f799b |
Try to also do a |
Actually, to be on the safe side, please do the following, then build again: $ git reset --hard HEAD
$ git clean -fdx |
FTR: |
I also see FTR, using the current HEAD of
|
cc @markshannon |
Those are preceded by I think like unused labels are suppressed in generated code, these should be suppressed, too. Lines 725 to 727 in f26daa9
and also added || defined(__clang_) to get rid of this warning in clang-cl based builds ...
|
For clang, can't we add |
"Regular" clangs react on I agree that patching |
I’m still able to reproduce the warnings with this workflow, which effectively eliminates the possibility that any custom settings or files are causing interference.
|
Bug report
Bug description:
I ran the
./configure
andmake
, here are the warnings shown.Operating System:
Main branch commit : 48c70b8
CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS
The text was updated successfully, but these errors were encountered: