This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/22570] Null Characters instead of blanks in text output.
- From: "stevenb at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 20 Jul 2005 20:17:02 -0000
- Subject: [Bug libfortran/22570] Null Characters instead of blanks in text output.
- References: <20050720153355.22570.dir@lanl.gov>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From stevenb at suse dot de 2005-07-20 20:17 -------
Subject: Re: Null Characters instead of blanks in text output.
On Wednesday 20 July 2005 22:03, Steven Bosscher wrote:
> On Wednesday 20 July 2005 21:07, Paul Thomas wrote:
> > pinskia at gcc dot gnu dot org wrote:
> > >------- Additional Comments From pinskia at gcc dot gnu dot org
> > > 2005-07-20 15:41 ------- Confirmed, I think this was caused by:
> > >2005-07-12 Paul Thomas <pault@gcc.gnu.org>
> >
> > Guilty, as charged.
> >
> > Please find attached, ChangeLog entries, patch, the output that was
> > incorrect and now looks the same as ifc, plus a testcase.
>
> This still doesn't fix mgrid either.
FWIW I get the feeling that the sixtrack and mgrid problems are
the same bug. For mgrid we have spurious '\0' characters in the
output, and for sixtrack a read of an internal file with a format
with an 'X' specifier in it ("READ(5,'(18X,I4)') NNO") fails...
I still haven't been able to reduce this to a useful testcase :-(
Gr.
Steven
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22570