#1321: GHCi stdout bug when base package is not optimised
-----------------------+----------------------------------------------------
Reporter: simonmar | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.8
Component: Compiler | Version: 6.7
Severity: normal | Keywords:
Difficulty: Unknown | Os: Unknown
Testcase: | Architecture: Unknown
-----------------------+----------------------------------------------------
Reported by Igloo:
The problem from a couple of weeks ago, where ghci's hFlush command
seems to be flushing a different stdout to the one that expressions
evaluated by ghci write to, happens with a "quickest" build:
{{{
SRC_HC_OPTS = -H64m -Onot -fasm
GhcStage1HcOpts = -O -fasm
GhcStage2HcOpts = -Onot -fasm
GhcLibHcOpts = -Onot -fasm
GhcLibWays =
SplitObjs = NO
}}}
but not if libraries are optimised:
{{{
SRC_HC_OPTS = -H64m -Onot -fasm
GhcStage1HcOpts = -O -fasm
GhcStage2HcOpts = -Onot -fasm
GhcLibHcOpts = -O -fasm
GhcLibWays =
SplitObjs = NO
}}}
ghci004 is an example of a failing test (no output is printed if
libraries are not optimised).
This seems completely illogical to me. I'd have expected such a bug
would be caused by optimisation meaning stdout gets inlined somewhere or
something. Very curious!
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1321>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
