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
enable extra compilation warnings #66308
Comments
The patch attached enables -Wsign-compare and -Wunreachable-code if supported by the compiler. As for unreachable code, it's also usually a good thing, since it can be a source of bugs. Note that it's not enabled in debug mode, since in debug mode the code paths aren't the same. |
+1 from me. |
The patch adds a a lot of new warnings. Would it be possible to fix them before applying the patch? |
Enabling the warnings may be a good incitation for other people to fix them ;) |
That was my intention... Can I push it, and let warnings be fixed on a case-by-case basis? |
Le 31/07/2014 13:51, Charles-François Natali a écrit :
+1 from me. |
New changeset 2c70897e5f98 by Charles-François Natali in branch 'default': |
Committed. |
GCC >=4.5.0 (released on 2010-04-14) silently accepts and ignores -Wunreachable-code option. I think that build system of Python should not pass unused options to compiler. |
See Issue bpo-24324 which modifies configure to not use -Wunreachable-code with gcc for the reasons stated there and by Arfrever above. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: