Segfault on x86 with -O2
jan.stolarek at p.lodz.pl
Wed Aug 14 10:05:31 CEST 2013
Lesson learned (for me at least): add regression tests to the testsuite when reporting compiler failures.
----- Oryginalna wiadomość -----
Od: "Kazu Yamamoto (山本和彦)" <kazu at iij.ad.jp>
Do: ghc-devs at haskell.org
Wysłane: środa, 14 sierpień 2013 7:39:10
Temat: Re: Segfault on x86 with -O2
It seems to me that #8116 (only for GHC head) was also fixed. :-)
> And just for the record, people reported this morning they couldn't
> reproduce #8103 anymore, and I'd bet this probably fixes that one,
> On Tue, Aug 13, 2013 at 10:17 PM, Austin Seipp <aseipp at pobox.com> wrote:
>> 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:
>>> Some changes in the last 8 days fixed segfault on 32bit x86 with -O2:
>>> I read recent log messages but I cannot guess which commits fixed this
>>> bug. Does anyone guess?
>>> 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.
>>> ghc-devs mailing list
>>> ghc-devs at haskell.org
>> Austin - PGP: 4096R/0x91384671
> Austin - PGP: 4096R/0x91384671
ghc-devs mailing list
ghc-devs at haskell.org
More information about the ghc-devs