public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31553] incorrect processing of formatted character output
Date: Thu, 12 Apr 2007 18:00:00 -0000	[thread overview]
Message-ID: <20070412180008.21472.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31553-11772@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from burnus at gcc dot gnu dot org  2007-04-12 19:00 -------
Which version are you using under i386-pc-mingw32? (I see "Reported against
4.3.0, however - see below.)

I'm asking because "4.0.3 (intel linux 64bit)" is very old. GCC 4.0.x contained
the freshly added and still a bit buggy gfortran. One should use version 4.1.x,
which is much more stable, or the 4.2.0 or 4.3.0 which contain even fewer
Fortran bugs. Binaries are available from:
http://gcc.gnu.org/wiki/GFortranBinaries

Using
  gfortran 4.1.3 20070302 (prerelease)
  gfortran 4.2.0 20070412 (prerelease)
  gfortran 4.3.0 20070412 (experimental)
I get the same result as with NAG f95, sunf95 and Intel ifort:

 (    4(a,' | '))
1234 | 12345678 | 1234567890123456 | 12345678901234567890 |
1234 | 12345678 | 1234567890123456 | 12345678901234567890 |
1234 | 12345678 | 1234567890123456 | 12345678901234567890 |
1234 | 12345678 | 1234567890123456 | 12345678901234567890 |


-- 


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


  parent reply	other threads:[~2007-04-12 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 17:12 [Bug fortran/31553] New: " brad dot finney at humboldt dot edu
2007-04-12 17:20 ` [Bug fortran/31553] " brad dot finney at humboldt dot edu
2007-04-12 17:22 ` brad dot finney at humboldt dot edu
2007-04-12 18:00 ` burnus at gcc dot gnu dot org [this message]
2007-04-12 19:29 ` brad dot finney at humboldt dot edu
2007-04-13 14:04 ` fxcoudert 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=20070412180008.21472.qmail@sourceware.org \
    --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).