public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41154]  New: [4.5 Regression] Comma required after P descriptor
Date: Mon, 24 Aug 2009 12:26:00 -0000	[thread overview]
Message-ID: <bug-41154-16146@http.gcc.gnu.org/bugzilla/> (raw)

With r151053 I get an error when I compile the following line:

2000 format (1X,1P,E14.6,3E12.4,0P)
                                   1
Error: Comma required after P descriptor in format string at (1)

While I haven't checked in the standard if this is really valid, it was
swallowed by gfortran until recently. It is also accepted by ifort and g95.

This was certainly introduced by Jerry's r151045.


-- 
           Summary: [4.5 Regression] Comma required after P descriptor
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41154


             reply	other threads:[~2009-08-24 12:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 12:26 janus at gcc dot gnu dot org [this message]
2009-08-24 13:46 ` [Bug fortran/41154] " burnus at gcc dot gnu dot org
2009-08-24 13:55 ` janus at gcc dot gnu dot org
2009-08-24 23:45 ` [Bug fortran/41154] New: " Jerry DeLisle
2009-08-24 23:45 ` [Bug fortran/41154] " jvdelisle at verizon dot net
2009-08-25  1:03 ` jvdelisle at gcc dot gnu dot org
2009-08-25  1:05 ` jvdelisle at gcc dot gnu dot org
2009-08-25  1:14 ` jvdelisle at gcc dot gnu dot org
2009-08-25  1:21 ` jvdelisle 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=bug-41154-16146@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).