public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50536] an input item shall not appear as the do-variable of any io-implied-do Date: Sat, 27 Feb 2021 08:53:57 +0000 [thread overview] Message-ID: <bug-50536-4-ERkIoDe3Hg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50536-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50536 --- Comment #9 from Vittorio Zecca <zeccav at gmail dot com> --- Still present in version 11. Detected by NAG nagfor and Intel ifort. [vitti f95]$nagfor -S -w gfbug74.f NAG Fortran Compiler Release 7.0(Yurakucho) Build 7042 Error: gfbug74.f, line 4: Input item L cannot also be an I/O implied DO variable [NAG Fortran Compiler error termination, 1 error] [vitti f95]$ifort -S -w gfbug74.f gfbug74.f(4): error #8251: An input item must not appear as the implied-DO variable of any implied-DO loop that contains the input item. [L] read *,(l,l=1,2) --------------^ compilation aborted for gfbug74.f (code 1)
prev parent reply other threads:[~2021-02-27 8:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-27 14:16 [Bug fortran/50536] New: " zeccav at gmail dot com 2012-01-23 7:25 ` [Bug fortran/50536] " kargl at gcc dot gnu.org 2013-06-20 18:39 ` dominiq at lps dot ens.fr 2013-06-20 22:18 ` kargl at gcc dot gnu.org 2013-06-20 22:25 ` dominiq at lps dot ens.fr 2013-07-20 20:23 ` burnus at gcc dot gnu.org 2013-07-20 20:29 ` burnus at gcc dot gnu.org 2013-07-21 9:50 ` burnus at gcc dot gnu.org 2021-02-27 8:53 ` zeccav at gmail dot com [this message]
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=bug-50536-4-ERkIoDe3Hg@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).