This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Ruby testsuite failures because of pointer mangling on 32-bit ARM?
- From: Will Newton <will dot newton at linaro dot org>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: David Miller <davem at davemloft dot net>, Andrew Pinski <pinskia at gmail dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Tue, 14 Jan 2014 09:37:12 +0000
- Subject: Re: Ruby testsuite failures because of pointer mangling on 32-bit ARM?
- Authentication-results: sourceware.org; auth=none
- References: <20131210 dot 211901 dot 1840879367475720601 dot davem at davemloft dot net> <52A94FB5 dot 7060100 at redhat dot com> <20131212 dot 121441 dot 261870704107659875 dot davem at davemloft dot net> <20131212 dot 132053 dot 446942135510037848 dot davem at davemloft dot net> <52AA2BAB dot 50309 at redhat dot com> <CANu=DmgxLAsGkdnka1rYpE_aoTa79c18aua5D9tjFRYvA8vsvQ at mail dot gmail dot com> <52AB2EDD dot 2080503 at redhat dot com> <52CC66EB dot 7020004 at redhat dot com>
On 7 January 2014 20:43, Carlos O'Donell <carlos@redhat.com> wrote:
Hi Carlos,
>>> If the frame pointer register is being used as a frame pointer it
>>> can't contain a data pointer. Likewise the stack pointer and lr. As
>>> far as i can tell the only issue is encrypting the frame pointer in
>>> the -fomit-frame-pointer case.
>>>
>>> Did the patch I submitted fix the ruby testsuite issue?
>>
>> I'm still verifying this. Perhaps wait to checkin the patch until I give
>> an all clear?
>
> I've handed a new set of packages to our ruby maintainer for verification.
>
> I'll let you know how it goes.
Any news on this? I have had other reports that it does indeed fix the issue.
Thanks,
--
Will Newton
Toolchain Working Group, Linaro