> With ghc-4.08.1, running on Linux with -0 -O2-for-C, I get:
>
> <<loop>>
>
> With ghc-4.08, running on Solaris, with -O -O2-for-C, I get:
>
> hsc: no threads to run: infinite loop or deadlock?
>
> With ghc-4.08, running on Solaris, with -Onot, the compilation works.
> For the sources you will need the whole of UniForM again,
> instructions on
> request. What is going on?
<<loop>> indicates a black hole - the RTS detected the main thread was
self-referential and raised the NonTermination exception, which is printed
as "<<loop>>". The test isn't foolproof, so sometimes you get the deadlock
message instead (but this needs some further investigation, it seems).
It's worrying that compiling without optimisation causes the program to
terminate correctly. This indicates a possible strictness analyser bug.
Ok, we'll need to investigate but this is going to be a tricky one to track
down. Is there any way you can try to narrow down the problem?
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
