Segfault on x86 with -O2

Austin Seipp aseipp at pobox.com
Wed Aug 14 05:17:38 CEST 2013


Kazu,

What about 3e598fe0b01f4692f50c377ac91010040227e7ce in ghc? This was a
calling convention bug that Geoffrey fixed.

It looks like it is almost certainly the culprit.

On Tue, Aug 13, 2013 at 10:14 PM, Kazu Yamamoto <kazu at iij.ad.jp> wrote:
> Hi,
>
> Some changes in the last 8 days fixed segfault on 32bit x86 with -O2:
>
>         http://ghc.haskell.org/trac/ghc/ticket/7953
>
> I read recent log messages but I cannot guess which commits fixed this
> bug. Does anyone guess?
>
> P.S.
>
> Thanks to this, now I started running Mighty with multicore IO manager
> on mew.org. I'm watching whether or not multicore IO manager works
> stably in the real world.
>
> --Kazu
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs



-- 
Regards,
Austin - PGP: 4096R/0x91384671




More information about the ghc-devs mailing list