Segfault on x86 with -O2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Kazu Yamamoto (山本和彦)
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



Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Austin Seipp-4
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



Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Austin Seipp-4
And just for the record, people reported this morning they couldn't
reproduce #8103 anymore, and I'd bet this probably fixes that one,
too.

On Tue, Aug 13, 2013 at 10:17 PM, Austin Seipp <aseipp at pobox.com> wrote:

> 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



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



Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Kazu Yamamoto (山本和彦)
Austin,

Great! Thank you!

--Kazu

> And just for the record, people reported this morning they couldn't
> reproduce #8103 anymore, and I'd bet this probably fixes that one,
> too.
>
> On Tue, Aug 13, 2013 at 10:17 PM, Austin Seipp <aseipp at pobox.com> wrote:
>> 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
>
>
>
> --
> Regards,
> Austin - PGP: 4096R/0x91384671



Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Kazu Yamamoto (山本和彦)
In reply to this post by Austin Seipp-4
Hi,

It seems to me that #8116 (only for GHC head) was also fixed. :-)

--Kazu

> And just for the record, people reported this morning they couldn't
> reproduce #8103 anymore, and I'd bet this probably fixes that one,
> too.
>
> On Tue, Aug 13, 2013 at 10:17 PM, Austin Seipp <aseipp at pobox.com> wrote:
>> 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
>
>
>
> --
> Regards,
> Austin - PGP: 4096R/0x91384671



Reply | Threaded
Open this post in threaded view
|

Segfault on x86 with -O2

Jan Stolarek
Lesson learned (for me at least): add regression tests to the testsuite when reporting compiler failures.

Janek

----- 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

Hi,

It seems to me that #8116 (only for GHC head) was also fixed. :-)

--Kazu

> And just for the record, people reported this morning they couldn't
> reproduce #8103 anymore, and I'd bet this probably fixes that one,
> too.
>
> On Tue, Aug 13, 2013 at 10:17 PM, Austin Seipp <aseipp at pobox.com> wrote:
>> 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
>
>
>
> --
> Regards,
> Austin - PGP: 4096R/0x91384671

_______________________________________________
ghc-devs mailing list
ghc-devs at haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs