public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/47434] Wrong field width for NaN with (F0.n) formatting
Date: Wed, 02 Feb 2011 18:16:00 -0000	[thread overview]
Message-ID: <bug-47434-4-mikVFIx1LF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47434-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Diego Novillo <dnovillo at gcc dot gnu.org> 2011-02-02 18:02:43 UTC ---
Author: dnovillo
Date: Wed Feb  2 18:02:38 2011
New Revision: 169687

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169687
Log:
2011-01-29  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

    PR libgfortran/47434
    * gfortran.dg/read_infnan_1.f90: Update test.
    * gfortran.dg/module_nan.f90: Update test.
    * gfortran.dg/char4_iunit_1.f03: Update test.
    * gfortran.dg/large_real_kind_1.f90: Update test.
    * gfortran.dg/real_const_3.f90: Update test.
    * gfortran.fortran-torture/execute/nan_inf_fmt.f90: Update test.

Modified:
    branches/google/integration/gcc/testsuite/ChangeLog
    branches/google/integration/gcc/testsuite/gfortran.dg/char4_iunit_1.f03
    branches/google/integration/gcc/testsuite/gfortran.dg/large_real_kind_1.f90
    branches/google/integration/gcc/testsuite/gfortran.dg/module_nan.f90
    branches/google/integration/gcc/testsuite/gfortran.dg/read_infnan_1.f90
    branches/google/integration/gcc/testsuite/gfortran.dg/real_const_3.f90
   
branches/google/integration/gcc/testsuite/gfortran.fortran-torture/execute/nan_inf_fmt.f90


      parent reply	other threads:[~2011-02-02 18:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 13:19 [Bug libfortran/47434] New: " thenlich at users dot sourceforge.net
2011-01-24 13:26 ` [Bug libfortran/47434] " jvdelisle at gcc dot gnu.org
2011-01-24 14:49 ` thenlich at users dot sourceforge.net
2011-01-27 13:23 ` jvdelisle at gcc dot gnu.org
2011-01-27 13:30 ` burnus at gcc dot gnu.org
2011-01-27 14:01 ` thenlich at users dot sourceforge.net
2011-01-27 14:03 ` burnus at gcc dot gnu.org
2011-01-27 16:51 ` jvdelisle at gcc dot gnu.org
2011-01-27 17:29 ` burnus at gcc dot gnu.org
2011-01-27 18:31 ` thenlich at users dot sourceforge.net
2011-01-29 17:37 ` jvdelisle at gcc dot gnu.org
2011-01-29 17:40 ` jvdelisle at gcc dot gnu.org
2011-01-29 19:29 ` jvdelisle at gcc dot gnu.org
2011-02-02 18:15 ` dnovillo at gcc dot gnu.org
2011-02-02 18:16 ` dnovillo at gcc dot gnu.org [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-47434-4-mikVFIx1LF@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).