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 libfortran/50105] [4.6/4.7 Regression] I/O with g6.5 - wrong number of "**" shown
Date: Fri, 19 Aug 2011 18:17:00 -0000 [thread overview]
Message-ID: <bug-50105-4-DsfAr5PPmv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50105-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50105
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Severity|normal |minor
--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-19 18:14:46 UTC ---
For completeness: FORTRAN 77 had a similar wording at
http://www.fortran.com/fortran/F77_std/rjcnf-13.html#sh-13.5.9
http://www.fortran.com/fortran/F77_std/rjcnf-13.html#sh-13.5.9.2.3
Bill is not convinced about Malcolm's answer:
http://j3-fortran.org/pipermail/j3/2011-August/004606.html
If I read it correctly, Bill thinks that one can read the standard such that
"** " is correct, but thinks that the standard is ambiguous and also allows
"******" which - according to his count - most compilers do and a user would
expect.
I think we will have at the end an interpretation request - thus, one might
leave this item open until after the J3 meeting or better after the balloting
of the J3 meeting edits. The next meeting is October 10-14, 2011.
next prev parent reply other threads:[~2011-08-19 18:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 6:22 [Bug libfortran/50105] New: Possibly: [4.3/4.4/4.5/4.6/4.7 " burnus at gcc dot gnu.org
2011-08-17 6:40 ` [Bug libfortran/50105] " burnus at gcc dot gnu.org
2011-08-17 7:34 ` burnus at gcc dot gnu.org
2011-08-17 7:53 ` thenlich at users dot sourceforge.net
2011-08-17 9:14 ` [Bug libfortran/50105] Possibly: [4.6/4.7 " burnus at gcc dot gnu.org
2011-08-17 13:27 ` burnus at gcc dot gnu.org
2011-08-18 8:59 ` [Bug libfortran/50105] Possibly: " burnus at gcc dot gnu.org
2011-08-19 6:54 ` [Bug libfortran/50105] [4.6/4.7 Regression] " burnus at gcc dot gnu.org
2011-08-19 11:17 ` burnus at gcc dot gnu.org
2011-08-19 18:17 ` burnus at gcc dot gnu.org [this message]
2011-08-22 6:07 ` jvdelisle at gcc dot gnu.org
2011-10-26 17:21 ` jakub at gcc dot gnu.org
2012-01-10 0:41 ` jvdelisle at gcc dot gnu.org
2012-01-10 8:46 ` burnus at gcc dot gnu.org
2012-01-10 19:33 ` jvdelisle at gcc dot gnu.org
2012-01-12 9:08 ` burnus at gcc dot gnu.org
2012-02-03 19:22 ` tkoenig at gcc dot gnu.org
2012-02-18 9:54 ` burnus at gcc dot gnu.org
2012-02-18 17:51 ` dominiq at lps dot ens.fr
2012-03-01 14:56 ` jakub at gcc dot gnu.org
2013-01-02 17:24 ` [Bug libfortran/50105] [4.6/4.7/4.8 " burnus at gcc dot gnu.org
2013-01-02 20:46 ` jvdelisle at gcc dot gnu.org
2013-01-02 21:40 ` anlauf at gmx dot de
2013-02-15 7:39 ` burnus 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-50105-4-DsfAr5PPmv@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).