public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/33863] backspace error on i386-pc-mingw32 Date: Sun, 04 Nov 2007 21:25:00 -0000 [thread overview] Message-ID: <20071104212512.16341.qmail@sourceware.org> (raw) In-Reply-To: <bug-33863-10129@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-11-04 21:25 ------- OK, I have taken some time to investigate this. The problem is not MSYS specific and also occurs with Cygwin. I do not think we can fix this. Its not a gfortran bug. The code is attempting to backspace a standard input stream. You can not seek backwards on an input stream. The code happens to work in some cases because input buffering happens to still contain the relevant data. Gfortran buffering hides the stream but you can not rely on it depending on how far you have to backspace If I modify the code slightly and open the input file directly, it works without error. This tels me its not a CR-LF issue. Any other opinions? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33863
next prev parent reply other threads:[~2007-11-04 21:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-22 18:59 [Bug libfortran/33863] New: " dir at lanl dot gov 2007-10-22 18:59 ` [Bug libfortran/33863] " dir at lanl dot gov 2007-10-22 19:00 ` dir at lanl dot gov 2007-10-22 23:11 ` jvdelisle at gcc dot gnu dot org 2007-10-30 4:19 ` jvdelisle at gcc dot gnu dot org 2007-10-30 12:59 ` dir at lanl dot gov 2007-11-04 21:25 ` jvdelisle at gcc dot gnu dot org [this message] 2007-11-08 19:56 ` dir at lanl dot gov 2007-11-08 23:51 ` fxcoudert at gcc dot gnu dot org 2007-11-23 17:15 ` 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=20071104212512.16341.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: linkBe 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).