--- Comment #9 from jvdelisle at gcc dot gnu dot org 2010-03-20 17:34
---
Closing, this was fixed some time ago.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #8 from kargl at gcc dot gnu dot org 2010-02-16 16:29 ---
(In reply to comment #6)
> Subject: RE: gfortran: spurious warning of line truncation at col 72
>
> > Well, it's a counting issue. Fixed-form Fortran is required to
> > have exactly 72 characters in a line of code.
--- Comment #7 from burnus at gcc dot gnu dot org 2010-02-16 16:25 ---
(In reply to comment #3)
> Mystery solved. It is to do with line endings. When gfortran sees
> a file with DOS line endings it interprets the CR and LF as separate
> characters. This is why demonstrating the effect
--- Comment #6 from patrick dot wallace at stfc dot ac dot uk 2010-02-16
16:10 ---
Subject: RE: gfortran: spurious warning of line truncation at col 72
> Well, it's a counting issue. Fixed-form Fortran is required to
> have exactly 72 characters in a line of code. Does CRLF count as
--- Comment #5 from kargl at gcc dot gnu dot org 2010-02-16 16:01 ---
(In reply to comment #4)
> Subject: Re: gfortran: spurious warning of line truncation
> at col 72
>
> On Tue, 16 Feb 2010, patrick dot wallace at stfc dot ac dot uk wrote:
>
> > Mystery solved. It is to do with li
--- Comment #4 from joseph at codesourcery dot com 2010-02-16 12:09 ---
Subject: Re: gfortran: spurious warning of line truncation
at col 72
On Tue, 16 Feb 2010, patrick dot wallace at stfc dot ac dot uk wrote:
> Mystery solved. It is to do with line endings. When gfortran sees
> a
--- Comment #3 from patrick dot wallace at stfc dot ac dot uk 2010-02-16
08:49 ---
Subject: RE: gfortran: spurious warning of line truncation at col 72
> Works for me with both 4.4.2 and trunk.
Mystery solved. It is to do with line endings. When gfortran sees
a file with DOS line e
--- Comment #2 from patrick dot wallace at stfc dot ac dot uk 2010-02-15
19:10 ---
Subject: RE: gfortran: spurious warning of line truncation at col 72
Hi,
Thanks for your rapid response.
> Works for me with both 4.4.2 and trunk.
The fault was reported by a collaborator in Austral
--- Comment #1 from kargl at gcc dot gnu dot org 2010-02-15 17:10 ---
Works for me with both 4.4.2 and trunk.
Can you attach a small self-contained example
that fails? The single line of code you posted
may have been mangled during the submission.
PS: Does the line of code you submitt
