public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/27046] [mingw32] mixed C-Fortran I/O doesn't flush
Date: Thu, 28 Sep 2006 22:34:00 -0000	[thread overview]
Message-ID: <20060928223438.32647.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27046-12481@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from fxcoudert at gcc dot gnu dot org  2006-09-28 22:34 -------
(In reply to comment #7)
> Changing main() in ctesti.c  to start with:
> int main(int argc, char** argv) {
>   setvbuf(stdout, NULL, _IOLBF, 0);
> 
> fixes the redirection problem.

After some more testing, this fix doesn't work in all cases (e.g. in a shell of
MSYS window). I'm closing this PR: after all, this is not a bug in the
compiler, mixed-languages code is supposed to correctly flush both I/O systems
after operations. I would have liked to provide a workaround, only there
doesn't appear to be anythink general and robust enough.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27046


      parent reply	other threads:[~2006-09-28 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 15:31 [Bug fortran/27046] New: gfortran print flush in dll mikko dot lyly at csc dot fi
2006-04-05 16:02 ` [Bug fortran/27046] " pinskia at gcc dot gnu dot org
2006-04-05 16:08 ` [Bug libfortran/27046] " pinskia at gcc dot gnu dot org
2006-04-25  6:04 ` fxcoudert at gcc dot gnu dot org
2006-05-21 14:04 ` [Bug libfortran/27046] [mingw32] " fxcoudert at gcc dot gnu dot org
2006-06-12 17:40 ` [Bug libfortran/27046] [mingw32] mixed C-Fortran I/O doesn't flush fxcoudert at gcc dot gnu dot org
2006-09-13  3:59 ` dannysmith at users dot sourceforge dot net
2006-09-13 10:10 ` dannysmith at users dot sourceforge dot net
2006-09-20  7:50 ` fxcoudert at gcc dot gnu dot org
2006-09-28 14:08 ` fxcoudert at gcc dot gnu dot org
2006-09-28 22:34 ` fxcoudert at gcc dot gnu dot org [this message]

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=20060928223438.32647.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).