From 803331a0192e36775cf2ab084dc253fb68650541 Mon Sep 17 00:00:00 2001
From: simonmar <unknown>
Date: Fri, 2 Jul 1999 09:31:54 +0000
Subject: [PATCH] [project @ 1999-07-02 09:31:54 by simonmar] Remove final
 fflush() - it seems to be incompatible with recent releases of Linux's libc
 implementation, and we don't use stdio in any case.

---
 ghc/rts/RtsStartup.c | 17 +----------------
 1 file changed, 1 insertion(+), 16 deletions(-)

diff --git a/ghc/rts/RtsStartup.c b/ghc/rts/RtsStartup.c
index e6583faa8f8d..aa84c0b85b54 100644
--- a/ghc/rts/RtsStartup.c
+++ b/ghc/rts/RtsStartup.c
@@ -1,5 +1,5 @@
 /* -----------------------------------------------------------------------------
- * $Id: RtsStartup.c,v 1.14 1999/06/29 13:04:40 panne Exp $
+ * $Id: RtsStartup.c,v 1.15 1999/07/02 09:31:54 simonmar Exp $
  *
  * (c) The GHC Team, 1998-1999
  *
@@ -169,21 +169,6 @@ shutdownHaskell(void)
   if (RtsFlags.TickyFlags.showTickyStats) PrintTickyInfo();
 #endif
 
-  /*
-    This fflush is important, because: if "main" just returns,
-    then we will end up in pre-supplied exit code that will close
-    streams and flush buffers.  In particular we have seen: it
-    will close fd 0 (stdin), then flush fd 1 (stdout), then <who
-    cares>...
-    
-    But if you're playing with sockets, that "close fd 0" might
-    suggest to the daemon that all is over, only to be presented
-    with more stuff on "fd 1" at the flush.
-    
-    The fflush avoids this sad possibility.
-   */
-  fflush(stdout);
-
   rts_has_started_up=0;
 }
 
-- 
GitLab