--- Comment #4 from pinskia at gcc dot gnu dot org 2006-02-22 14:32 ---
(In reply to comment #2)
Still, it would be lots better if warning options simply enabled the necessary
analysis.
It is very hard to do so as the warnings are based on the information gathered
from
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-02-22 03:40 ---
HUH?
From:
http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Warning-Options.html#Warning-Options
This option is only active when -fstrict-aliasing is active.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26411
--- Comment #2 from acahalan at gmail dot com 2006-02-22 04:16 ---
Oops, it is indeed documented. Sorry. (recent change?)
Still, it would be lots better if warning options simply enabled the necessary
analysis.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26411
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-02-22 04:48 ---
(In reply to comment #2)
Oops, it is indeed documented. Sorry. (recent change?)
No it is not a recent change, it has been there since the option was added back
in 3.3:
