public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/59771] Cleanup handling of Gw.0 and Gw.0Ee format
Date: Sat, 11 Jan 2014 21:54:00 -0000	[thread overview]
Message-ID: <bug-59771-4-Y9qOfpGx8U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59771-4@http.gcc.gnu.org/bugzilla/>

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

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-11
     Ever confirmed|0                           |1

--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
A simple test case:

 PRINT '(6(1X,1PG9.0e2))', 0.0, 0.04, 0.06, 0.4, 0.6, 243.0
 PRINT '(6(1X,1PE9.0e2))', 0.0, 0.04, 0.06, 0.4, 0.6, 243.0

end

Without patch:

 ./a.out 
At line 1 of file pr48906.f90 (unit = 6, file = 'stdout')
Internal Error: Unspecified precision

With patch:

 ./a.out 
    0.E+00    4.E-02    6.E-02    4.E-01    6.E-01    2.E+02
    0.E+00    4.E-02    6.E-02    4.E-01    6.E-01    2.E+02


  reply	other threads:[~2014-01-11 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 21:49 [Bug libfortran/59771] New: " jvdelisle at gcc dot gnu.org
2014-01-11 21:54 ` jvdelisle at gcc dot gnu.org [this message]
2014-01-19 23:18 ` [Bug libfortran/59771] " jvdelisle at gcc dot gnu.org
2014-01-19 23:21 ` jvdelisle at gcc dot gnu.org
2014-02-15 15:49 ` jvdelisle at gcc dot gnu.org
2014-02-15 15:58 ` jvdelisle at gcc dot gnu.org
2014-02-15 16:53 ` jvdelisle at gcc dot gnu.org
2014-02-15 16:55 ` jvdelisle at gcc dot gnu.org
2014-02-15 17:26 ` jvdelisle 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-59771-4-Y9qOfpGx8U@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).