This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46166] optimization and/or removing an if(.false.) statement leads to bad results
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 26 Oct 2010 15:13:24 +0000
- Subject: [Bug fortran/46166] optimization and/or removing an if(.false.) statement leads to bad results
- Auto-submitted: auto-generated
- References: <bug-46166-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46166
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #5 from janus at gcc dot gnu.org 2010-10-26 15:13:14 UTC ---
(In reply to comment #4)
> The problem is tauc is used
> before it is initialized. This is a bogus
> bug report.
Why don't we just close it then?