public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/19071] New: complex formatted output has too many items
Date: Sat, 18 Dec 2004 19:20:00 -0000	[thread overview]
Message-ID: <20041218192037.19071.Thomas.Koenig@online.de> (raw)

$ cat cio.f
      program cio
      complex a
      a = cmplx(1.0, 2.0)
      print '(1P,E13.5)',a
      end
$ gfortran cio.f
$ ./a.out
  1.00000E+00  2.00000E+00
$ g77 cio.f
$ ./a.out
  1.00000E+00
  2.00000E+00
$ gfortran -v
Reading specs from /home/ig25/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
Configured with: ../gcc/configure --prefix=/home/ig25 --enable-languages=c,c++,f95
Thread model: posix
gcc version 4.0.0 20041218 (experimental)

Possibly related to PR 10964.

-- 
           Summary: complex formatted output has too many items
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Thomas dot Koenig at online dot de
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-12-18 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-18 19:20 Thomas dot Koenig at online dot de [this message]
2004-12-18 19:21 ` [Bug libfortran/19071] " Thomas dot Koenig at online dot de
2004-12-20 16:10 ` tobi at gcc dot gnu dot org
2004-12-24  0:14 ` bdavis at gcc dot gnu dot org
2004-12-24  0:29 ` cvs-commit at gcc dot gnu dot org
2004-12-24  1:34 ` pinskia 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=20041218192037.19071.Thomas.Koenig@online.de \
    --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).