--- 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 docu
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-02-07 16:39 ---
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
--- Comment #4 from tvb at gnome dot org 2007-02-07 14:59 ---
(In reply to comment #3)
> What is there to warn about?
> If you do -Winitialize without -O, you get a warning so ...
>
I just tried the explicit -Wuninitialized, very good,
and I noticed at least its documented in the man
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-02-06 22:03 ---
What is there to warn about?
If you do -Winitialize without -O, you get a warning so ...
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from tvb at gnome dot org 2007-02-06 20:09 ---
(In reply to comment #1)
> > If there is no reason to ever compile without -O,
>
> There are reasons, like getting much, much better debug info.
> -O1 enables lots of optimization that changes the code so much that debugging
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-02-06 19:48 ---
> If there is no reason to ever compile without -O,
There are reasons, like getting much, much better debug info.
-O1 enables lots of optimization that changes the code so much that debugging
optimizated code is har
