[ ghc-Bugs-955386 ] Unhelpful panic (incorrect flag)

2004-05-17 Thread SourceForge.net
Bugs item #955386, was opened at 2004-05-17 20:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108032&aid=955386&group_id=8032 Category: Compiler Group: 6.2.1 Status: Open Resolution: No

RE: compiling PrimOp.lhs

2004-05-17 Thread Simon Marlow
On 17 May 2004 09:05, Simon Peyton-Jones wrote: > I advise against giving -H flags to GHC if you have plenty of memory. > Might push up your GC time a lot. I think you mean -M. The -H flag just increases the default heap size, and can only make compilation faster (ignoring cache effects). The -

RE: internal error

2004-05-17 Thread Simon Peyton-Jones
Please remember that to test the 6.2-branch compiler (which is what you are trying to do) you cannot use a 6.2.1 ghci. You must say $(build)/fptools/ghc/compiler/stage2/ghc-inplace --interactive where $(build) is your build tree for the 6.2 branch. That gives you a 6.2 branch ghci Simon

RE: ghc-6-2-branch `internal error'

2004-05-17 Thread Simon Peyton-Jones
There is a known bug in the one-space compacting garbage collector for GHC 6.2.1. It is fixed in the 6.2 branch. This bug is shown up by your "space=XXX" choice. If you omit space=xxx you won't use the one-space collector, and the bug will probably vanish. I am not sure why you use it. Still, i

internal error: scavenge:

2004-05-17 Thread Serge D. Mechveliani
It also appears when a particular instance in Pol3_ is replaced with what ghc required earlier. > test "log" > ghc-6.2.1: internal error: scavenge: unimplemented/strange closure type 64 @ 0x40603330 --- It also appears under -Onot > :set +srem

internal error

2004-05-17 Thread Serge D. Mechveliani
Addition to my previous two reports: * this "internal error" also happens in the test ghci when docon is compiled under -Onot too. * But I tried > :set +s before> test "log" , and with this, the test completed successfully. - Serge Mechveliani [EMAIL P

cvs ghc-6.2.. internal error

2004-05-17 Thread Serge D. Mechveliani
And it also appears at the run-time. `Making' docon-2.08-pre (like in previous report enclosed) under -O, making the test by cd $(s)/demotest ghc $pcpdocon --make T_ and running the test byghci $pcpdocon T_ +RTS any space -RTS

ghc-6-2-branch `internal error'

2004-05-17 Thread Serge D. Mechveliani
Dear GHC developers, I have `made' GHC of cvs update -r ghc-6-2-branch(about May 14) by ghc-6.2.1 on RedHat Linux (about version 8) libc-2.2, i686. Now, you have the docon-2.08-pre test, with Pol3_.hs containing instance (LinSolvRing (Pol a), CommutativeRing a) =

RE: compiling PrimOp.lhs

2004-05-17 Thread Simon Peyton-Jones
I advise against giving -H flags to GHC if you have plenty of memory. Might push up your GC time a lot. I have absolutely no idea why GHC keeps getting re-invoked. You could try cd'ing to ghc/compiler and uttering the command line that compiles PrimOp.lhs manually. Does that continually reinvoke