public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters.
@ 2005-12-05 21:13 dir at lanl dot gov
2005-12-05 21:16 ` [Bug libfortran/25271] " dir at lanl dot gov
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: dir at lanl dot gov @ 2005-12-05 21:13 UTC (permalink / raw)
To: gcc-bugs
g77 prints correctly, but gfortran fails to correctly pad lines in format
statements to 72 characters. The lines in the file are terminated with a line
feed after the last printable character. If the lines are padded with blanks
out beyond 72 characters gfortran then prints correctly. This was fixed before
-
[dranta:~/tests/gfortran-D] dir% g77 -o write07 write07.f
[dranta:~/tests/gfortran-D] dir% write07
1
f o l l o w i n g i s a c a r d i m a g e l i s t i n
g o f t h e i n p u t d a t a
c o l u m n n u m
b e r
card 1 2 3 4
5 6 7 8
number
12345678901234567890123456789012345678901234567890123456789012345678901234567890
------
--------------------------------------------------------------------------------
0 ********************************** e n d o f i n p u t l i
s t i n g **********************************
[dranta:~/tests/gfortran-D] dir% gfortran -o write07 write07.f
[dranta:~/tests/gfortran-D] dir% write07
1
f o l l o w i n g i s a c a r d i m a g e l i s t i n
g o f t h e i n p u t d a t a
c o l u m n n u m
b e r
card 1 2 3 4 5
6 7 8 / number
12345678901234567890123456789012345678901234567890123456789012345678901234567890
------
--------------------------------------------------------------------------------
0 ********************************** e n d o f i n p u t l i
s t in g ,**********************************
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20051205 (experimental)
[dranta:~/tests/gfortran-D] dir% cat write07.f
program main
write(6,2000)
write(6,2030)
2000 format(1h1/10x,111hf o l l o w i n g i s a c a r d i m
1 a g e l i s t i n g o f t h e i n p u t d a t a //
t58x,26hc o l u m n n u m b e r,/20x,4hcard,16x,71h1 2
x 3 4 5 6 7 8 /
y19x,6hnumber, 6x,80h1234567890123456789012345678901234567890123456
z7890123456789012345678901234567890 /,19x,6(1h-),6x,80(1h-))
2030 format(1h0,10x,34(1h*),44h e n d o f i n p u t l i s t i
1n g ,34(1h*))
c
end
--
Summary: gfortran fails to pad lines in format statements to 72
characters.
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
GCC host triplet: powerpc-apple-darwin8.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
@ 2005-12-05 21:16 ` dir at lanl dot gov
2005-12-06 2:27 ` jvdelisle at gcc dot gnu dot org
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: dir at lanl dot gov @ 2005-12-05 21:16 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from dir at lanl dot gov 2005-12-05 21:16 -------
Created an attachment (id=10411)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10411&action=view)
problem file
This is the original problem file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
2005-12-05 21:16 ` [Bug libfortran/25271] " dir at lanl dot gov
@ 2005-12-06 2:27 ` jvdelisle at gcc dot gnu dot org
2005-12-06 13:47 ` dir at lanl dot gov
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: jvdelisle at gcc dot gnu dot org @ 2005-12-06 2:27 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-06 02:27 -------
I see that g77 output differs from gfortran.
I also see gfortran and ifort agree 100%.
I am not sure which is right.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
2005-12-05 21:16 ` [Bug libfortran/25271] " dir at lanl dot gov
2005-12-06 2:27 ` jvdelisle at gcc dot gnu dot org
@ 2005-12-06 13:47 ` dir at lanl dot gov
2005-12-08 12:41 ` tobi at gcc dot gnu dot org
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: dir at lanl dot gov @ 2005-12-06 13:47 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from dir at lanl dot gov 2005-12-06 13:47 -------
If you look at the output from format 2030, you will see that that comma at the
end of the "44h e n d..." statement is printed, but the comma is the 45th
character after the 44h . Like wise the '/' after the 8 is printed inspite of
being the 73 character after the start of the 71h format.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
` (2 preceding siblings ...)
2005-12-06 13:47 ` dir at lanl dot gov
@ 2005-12-08 12:41 ` tobi at gcc dot gnu dot org
2005-12-08 14:16 ` dir at lanl dot gov
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: tobi at gcc dot gnu dot org @ 2005-12-08 12:41 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from tobi at gcc dot gnu dot org 2005-12-08 12:41 -------
The lines are padded (see scanner.c:810), but this doesn't make it into the
format string, which could be construed to be a bug, but since this is not
something required by the standard (at least I think this was the consensus the
last time this came up) I'm downgrading this to enhancement.
--
tobi at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tobi at gcc dot gnu dot org
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2005-12-08 12:41:33
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
` (3 preceding siblings ...)
2005-12-08 12:41 ` tobi at gcc dot gnu dot org
@ 2005-12-08 14:16 ` dir at lanl dot gov
2006-07-06 21:00 ` [Bug fortran/25271] " fxcoudert at gcc dot gnu dot org
2007-12-08 15:46 ` fxcoudert at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: dir at lanl dot gov @ 2005-12-08 14:16 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from dir at lanl dot gov 2005-12-08 14:16 -------
Your are likely correct - it probability is not in the standard, but for the
first 15 years of FORTRAN, keypunches and card readers were the only way to
create and submit a program and they always pad to 80 characters - by
definition a line of FORTRAN was 80 character - since a card reader was the
only way to get a program to the computer. If the modern text editors, that
mostly truncate as they please had been around - the padding requirement would
have been in the standard. Actually, I am surprized that FORTRAN 77 did not add
that requirement to the standard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
` (4 preceding siblings ...)
2005-12-08 14:16 ` dir at lanl dot gov
@ 2006-07-06 21:00 ` fxcoudert at gcc dot gnu dot org
2007-12-08 15:46 ` fxcoudert at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2006-07-06 21:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from fxcoudert at gcc dot gnu dot org 2006-07-06 21:00 -------
Unless I'm severely mistaken, this is not library issue but a front-end issue.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|libfortran |fortran
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/25271] gfortran fails to pad lines in format statements to 72 characters.
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
` (5 preceding siblings ...)
2006-07-06 21:00 ` [Bug fortran/25271] " fxcoudert at gcc dot gnu dot org
@ 2007-12-08 15:46 ` fxcoudert at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-12-08 15:46 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from fxcoudert at gcc dot gnu dot org 2007-12-08 15:45 -------
Not standard and probably requires quite some work to get it working; closing
as WONTFIX, as per http://gcc.gnu.org/ml/fortran/2007-10/msg00263.html. If
someone comes up with a patch, it'll be of course be considered, but we don't
intend to provide one.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-12-08 15:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-12-05 21:13 [Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters dir at lanl dot gov
2005-12-05 21:16 ` [Bug libfortran/25271] " dir at lanl dot gov
2005-12-06 2:27 ` jvdelisle at gcc dot gnu dot org
2005-12-06 13:47 ` dir at lanl dot gov
2005-12-08 12:41 ` tobi at gcc dot gnu dot org
2005-12-08 14:16 ` dir at lanl dot gov
2006-07-06 21:00 ` [Bug fortran/25271] " fxcoudert at gcc dot gnu dot org
2007-12-08 15:46 ` 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).