This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/30719] gcc should probably warn if users compile without -O
- From: "tvb at gnome dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Feb 2007 16:48:25 -0000
- Subject: [Bug c/30719] gcc should probably warn if users compile without -O
- References: <bug-30719-14060@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from tvb at gnome dot org 2007-02-07 16:48 -------
(In reply to comment #5)
> To me a warning should not be emitted while using -Wall -O0 as it will break
> all the programs which use -Werror which is a lot of them. Also this is
> already documented, if people don't read documentation, why would they read
> warnings?
If they are using -Werror and insist on using -O0, then they can go
ahead and specify what warnings they want to ignore, they asked
for it by specifying -Werror.
If documentation were enough, I'm sure there wouldnt be
a warning for -Wuninitialized -O0, but there is, for obvious
reasons - people generally use a build system which typically
uses -Wall by default and generally people dont interface with gcc
directly.
- Most of the time people need to be warned
- People compiling with -Werror have a closer relationship
to the compiler and are better situated to deal with
the warning that should be appearing for -Wall -O0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30719