public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/31553] New: incorrect processing of formatted character output
@ 2007-04-12 17:12 brad dot finney at humboldt dot edu
2007-04-12 17:20 ` [Bug fortran/31553] " brad dot finney at humboldt dot edu
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: brad dot finney at humboldt dot edu @ 2007-04-12 17:12 UTC (permalink / raw)
To: gcc-bugs
"a" edit descriptor for character output produces repeatable, but incorrect
output in some situations when the width of the field is not explicitly
specified in the edit descriptor, but is inferred from the number of characters
in the write list item.
--
Summary: incorrect processing of formatted character output
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: brad dot finney at humboldt dot edu
GCC build triplet: 4.3.0
GCC host triplet: i386-pc-mingw32
GCC target triplet: i386-pc-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug fortran/31553] incorrect processing of formatted character output
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output brad dot finney at humboldt dot edu
@ 2007-04-12 17:20 ` brad dot finney at humboldt dot edu
2007-04-12 17:22 ` brad dot finney at humboldt dot edu
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: brad dot finney at humboldt dot edu @ 2007-04-12 17:20 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from brad dot finney at humboldt dot edu 2007-04-12 18:20 -------
Created an attachment (id=13359)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13359&action=view)
test program demonstrating bug behavior along with program output
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug fortran/31553] incorrect processing of formatted character output
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output 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
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: brad dot finney at humboldt dot edu @ 2007-04-12 17:22 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from brad dot finney at humboldt dot edu 2007-04-12 18:22 -------
same bug noted on version 4.0.3 (intel linux 64bit) noted.
--
brad dot finney at humboldt dot edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brad dot finney at humboldt
| |dot edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug fortran/31553] incorrect processing of formatted character output
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output 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
2007-04-12 19:29 ` brad dot finney at humboldt dot edu
2007-04-13 14:04 ` fxcoudert at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2007-04-12 18:00 UTC (permalink / raw)
To: gcc-bugs
------- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/31553] incorrect processing of formatted character output
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output brad dot finney at humboldt dot edu
` (2 preceding siblings ...)
2007-04-12 18:00 ` burnus at gcc dot gnu dot org
@ 2007-04-12 19:29 ` brad dot finney at humboldt dot edu
2007-04-13 14:04 ` fxcoudert at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: brad dot finney at humboldt dot edu @ 2007-04-12 19:29 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from brad dot finney at humboldt dot edu 2007-04-12 20:29 -------
(In reply to comment #3)
> Which version are you using under i386-pc-mingw32? (I see "Reported against
> 4.3.0, however - see below.)
>
gcc version 4.3.0 20061021
I had not tried on the latest version, so I apologize for posting a problem
that has already been corrected.
> 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 |
>
As do I with version 4.3.0 20070406
Thanks, and again sorry. I did check the list of bugs first, but didn't see
one that seemed to fit.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug fortran/31553] incorrect processing of formatted character output
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output brad dot finney at humboldt dot edu
` (3 preceding siblings ...)
2007-04-12 19:29 ` brad dot finney at humboldt dot edu
@ 2007-04-13 14:04 ` fxcoudert at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-04-13 14:04 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from fxcoudert at gcc dot gnu dot org 2007-04-13 15:04 -------
Closing according to comments.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31553
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-04-13 14:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-04-12 17:12 [Bug fortran/31553] New: incorrect processing of formatted character output 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
2007-04-12 19:29 ` brad dot finney at humboldt dot edu
2007-04-13 14:04 ` fxcoudert at gcc dot gnu dot org
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).