This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/44354] implied do loop with its own variable name as upper bound
- From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Jun 2010 18:11:12 -0000
- Subject: [Bug fortran/44354] implied do loop with its own variable name as upper bound
- References: <bug-44354-19262@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #22 from tkoenig at gcc dot gnu dot org 2010-06-07 18:11 -------
Adjusting subject, setting severity to "enhancement" and
adding "diagnostic" keyword.(In reply to comment #21)
> (In reply to comment #18)
> > Expected:
> > a) Allow it as extension (-std=gnu or -std=legacy; especially, for -std=gnu one
> > could consider a default-enabled warning)
> > b) Reject it for -std=f(95,2003,2008)
>
> I'd vote to reject it for any -std=*. This extension just asks for trouble.
I concur. I would also favor a warning at least for -Wuninitialized.
--
tkoenig at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu dot
| |org
Severity|normal |enhancement
Keywords| |diagnostic
Summary|incorrect output at run time|implied do loop with its own
| |variable name as upper bound
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44354