public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44354] incorrect output at run time
Date: Tue, 01 Jun 2010 03:47:00 -0000 [thread overview]
Message-ID: <20100601034655.23617.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44354-19262@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from jvdelisle at verizon dot net 2010-06-01 03:46 -------
Subject: Re: incorrect output at run time
On 05/31/2010 08:07 PM, sgk at troutmask dot apl dot washington dot edu wrote:
> ------- Comment #15 from sgk at troutmask dot apl dot washington dot edu 2010-06-01 03:07 -------
> Subject: Re: incorrect output at run time
>
> On Tue, Jun 01, 2010 at 02:09:38AM -0000, jvdelisle at gcc dot gnu dot org
> wrote:
>>
>> My take on this as I was reading through this thread before I got to comment
>> #13 is that the code has to be illegal. I vote for the error. I think it would
>> be bad practice too introduce this as an extension or for some other reason.
>>
>
> Note that
>
> i = 5
> print *, (i,i=1,i)
> end
>
> is valid Fortran and gfortran currently gives the expected
> result. The distinction is the above is an io-implied-do.
> The original code contains an ac-implied-do.
>
>
Understood!
Jerry
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44354
next prev parent reply other threads:[~2010-06-01 3:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 16:32 [Bug fortran/44354] New: " zeccav at gmail dot com
2010-05-31 17:43 ` [Bug fortran/44354] " mikael at gcc dot gnu dot org
2010-05-31 18:01 ` dominiq at lps dot ens dot fr
2010-05-31 18:04 ` mikael at gcc dot gnu dot org
2010-05-31 18:34 ` kargl at gcc dot gnu dot org
2010-05-31 19:24 ` dominiq at lps dot ens dot fr
2010-05-31 20:02 ` kargl at gcc dot gnu dot org
2010-05-31 21:31 ` mikael at gcc dot gnu dot org
2010-05-31 21:34 ` mikael at gcc dot gnu dot org
2010-05-31 21:38 ` zeccav at gmail dot com
2010-05-31 21:39 ` mikael at gcc dot gnu dot org
2010-05-31 21:54 ` kargl at gcc dot gnu dot org
2010-05-31 22:47 ` kargl at gcc dot gnu dot org
2010-05-31 23:44 ` kargl at gcc dot gnu dot org
2010-06-01 2:09 ` jvdelisle at gcc dot gnu dot org
2010-06-01 3:07 ` sgk at troutmask dot apl dot washington dot edu
2010-06-01 3:47 ` jvdelisle at verizon dot net [this message]
2010-06-01 4:31 ` pault at gcc dot gnu dot org
2010-06-01 8:03 ` burnus at gcc dot gnu dot org
2010-06-01 14:09 ` mikael at gcc dot gnu dot org
2010-06-01 14:14 ` mikael at gcc dot gnu dot org
2010-06-01 21:03 ` dfranke at gcc dot gnu dot org
2010-06-07 18:11 ` [Bug fortran/44354] implied do loop with its own variable name as upper bound tkoenig at gcc dot gnu dot org
2010-07-28 20:54 ` mikael at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100601034655.23617.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).