public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot a dot richmond at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41168] incorrect processing of formatted records in mingw port
Date: Thu, 03 Sep 2009 18:12:00 -0000 [thread overview]
Message-ID: <20090903181224.10826.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41168-14284@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from michael dot a dot richmond at nasa dot gov 2009-09-03 18:12 -------
(In reply to comment #4)
> It's probably some bad counting of position on platforms with HAVE_CRLF. To
> investigate, it should be possible to build such a faulty linux compiler by
> forcing HAVE_CRLF to be true.
I tried to do this in the i686-pc-linux-gnu port of gfortran. In the file
libgfortran/config.h.in I changed "#undef HAVE_CRLF" to "#define HAVE_CRLF".
When I built gfortran, the change was propagated to libgfortran/config.h. But
when I ran the test case it created a file with standard Linux carriage
control.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41168
next prev parent reply other threads:[~2009-09-03 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:26 [Bug fortran/41168] New: " michael dot a dot richmond at nasa dot gov
2009-08-26 0:39 ` [Bug fortran/41168] " jvdelisle at gcc dot gnu dot org
2009-08-26 1:03 ` jvdelisle at gcc dot gnu dot org
2009-08-26 16:47 ` michael dot a dot richmond at nasa dot gov
2009-09-03 14:19 ` fxcoudert at gcc dot gnu dot org
2009-09-03 18:12 ` michael dot a dot richmond at nasa dot gov [this message]
2009-09-04 23:09 ` jvdelisle at gcc dot gnu dot org
2009-09-08 10:04 ` burnus at gcc dot gnu dot org
2009-09-08 15:21 ` michael dot a dot richmond at nasa dot gov
2009-09-09 0:58 ` jvdelisle at gcc dot gnu dot org
2009-09-09 2:12 ` jvdelisle at gcc dot gnu dot org
2009-09-11 5:38 ` jvdelisle 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=20090903181224.10826.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).