public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/63744] [4.8/4.9/5 Regression] Duplicate use-statement causes error
Date: Sat, 15 Nov 2014 15:42:00 -0000 [thread overview]
Message-ID: <bug-63744-4-44GSYojODX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63744-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63744
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|rejects-valid |
CC| |burnus at gcc dot gnu.org
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Dominque, as you changed:
- Status: UNCONFIRMED
+ Status: NEW
+ Keywords: rejects-valid
Can you quote the standard which permits this? My feeling is that the code is
invalid, but I have to admit that it is only a feeling.
next prev parent reply other threads:[~2014-11-15 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 8:46 [Bug fortran/63744] New: " roger.ferrer at bsc dot es
2014-11-15 15:06 ` [Bug fortran/63744] [4.8/4.9/5 Regression] " dominiq at lps dot ens.fr
2014-11-15 15:42 ` burnus at gcc dot gnu.org [this message]
2014-11-15 16:14 ` dominiq at lps dot ens.fr
2014-11-15 17:00 ` burnus at gcc dot gnu.org
2014-11-15 17:04 ` dominiq at lps dot ens.fr
2014-11-19 13:28 ` rguenth at gcc dot gnu.org
2014-11-20 11:36 ` jakub at gcc dot gnu.org
2014-12-19 13:44 ` jakub at gcc dot gnu.org
2015-02-03 14:49 ` mikael at gcc dot gnu.org
2015-02-06 20:01 ` mikael at gcc dot gnu.org
2015-02-08 14:18 ` mikael at gcc dot gnu.org
2015-02-13 18:49 ` mikael at gcc dot gnu.org
2015-02-13 19:34 ` mikael at gcc dot gnu.org
2015-02-13 20:07 ` mikael at gcc dot gnu.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=bug-63744-4-44GSYojODX@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: 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).