This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/36902] Array bound warning with dead code after optimization
- From: "hjl dot tools at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Aug 2008 17:37:12 -0000
- Subject: [Bug middle-end/36902] Array bound warning with dead code after optimization
- References: <bug-36902-682@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from hjl dot tools at gmail dot com 2008-08-22 17:37 -------
(In reply to comment #19)
> (In reply to comment #18)
> > I think that if the compiler knows that the code is never executed then, we
> > shouldn't warn.
>
> It does but only later on in the optimization it knows that the code is dead.
>
Why can't we queue those warnings which may come from dead code and
suppress them if they are dead?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36902