From: Matt Turner <mattst88@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Richard Henderson <rth@twiddle.net>,
libc-ports@sourceware.org, Mike Frysinger <vapier@gentoo.org>,
Gentoo alpha AT <alpha@gentoo.org>
Subject: Re: Signal handling broken on alpha since glibc-2.16
Date: Thu, 14 Nov 2013 16:43:00 -0000 [thread overview]
Message-ID: <CAEdQ38HNXss1h58n4+ar2dWZtv8KPycoyrhvnogfbt2RbdNOrA@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4Z_DswBeGmVJ3ZYfO3DV88c9M+gDr2Vk4VETjWvpZ96eA@mail.gmail.com>
On Wed, Nov 13, 2013 at 11:27 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Thu, Nov 14, 2013 at 3:18 AM, Matt Turner <mattst88@gmail.com> wrote:
>> On Wed, Nov 13, 2013 at 2:50 PM, Richard Henderson <rth@twiddle.net> wrote:
>>> On 11/04/2013 11:10 AM, Matt Turner wrote:
>>>> A test from the gcc test suite shows that signal handling is broken on
>>>> alpha since glibc-2.16. Bisecting before the glibc-ports merge is
>>>> rather hard.
>>>>
>>>> See: https://bugs.gentoo.org/show_bug.cgi?id=480740 (includes test case)
>>>>
>>>> Off hand, do any changes between 2.15 and 2.16 seem to be likely
>>>> candidates to cause this bug?
>>>
>>> It's likely to be change 7d1feb5693be7e606104cc2b6657c746a93e5926.
>>>
>>> Please try this.
>>
>> Looks like it works here. Thanks!
>>
>> RA = 0x120000c44, CFA = 0x11fc9e800
>> RA = 0x120000c78, CFA = 0x11fc9e810
>> RA = 0x200000b49d0, CFA = 0x11fc9e820
>> RA = 0x120000aac, CFA = 0x11fc9eb58
>> RA = 0x120000b38, CFA = 0x11fc9eb90
>> RA = 0x120000b58, CFA = 0x11fc9ec30
>> RA = 0x1200008e8, CFA = 0x11fc9ec40
>> RA = 0x2000009ad00, CFA = 0x11fc9ec50
>> Aborted
>
> The test should not abort. Did you compiled it with -fexceptions
> -fnon-call-exceptions?
Whoops. Compiling with the proper CFLAGS leads to better results:
RA = 0x120000bdc, CFA = 0x11f8f8f00
RA = 0x120000c14, CFA = 0x11f8f8f00
RA = 0x120000c38, CFA = 0x11f8f8f10
RA = 0x120000c5c, CFA = 0x11f8f8f10
RA = 0x2000009e9d0, CFA = 0x11f8f8f20
RA = 0x120000aec, CFA = 0x11f8f9258
RA = 0x120000b84, CFA = 0x11f8f9280
RA = 0x120000d28, CFA = 0x11f8f9320
Thanks.
next prev parent reply other threads:[~2013-11-14 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 1:11 Matt Turner
2013-11-13 22:52 ` Richard Henderson
2013-11-14 2:18 ` Matt Turner
2013-11-14 7:27 ` Uros Bizjak
2013-11-14 16:43 ` Matt Turner [this message]
2013-11-14 17:29 ` Uros Bizjak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEdQ38HNXss1h58n4+ar2dWZtv8KPycoyrhvnogfbt2RbdNOrA@mail.gmail.com \
--to=mattst88@gmail.com \
--cc=alpha@gentoo.org \
--cc=libc-ports@sourceware.org \
--cc=rth@twiddle.net \
--cc=ubizjak@gmail.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).