This is the mail archive of the
mailing list for the libc-ports project.
Re: [PATCH] ARM: Don't apply pointer encryption to the frame pointer
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>, Will Newton <will dot newton at linaro dot org>
- Cc: libc-ports at sourceware dot org, Patch Tracking <patches at linaro dot org>
- Date: Tue, 10 Dec 2013 13:57:32 -0500
- Subject: Re: [PATCH] ARM: Don't apply pointer encryption to the frame pointer
- Authentication-results: sourceware.org; auth=none
- References: <52A74F24 dot 8000805 at linaro dot org> <Pine dot LNX dot 4 dot 64 dot 1312101806240 dot 15324 at digraph dot polyomino dot org dot uk>
On 12/10/2013 01:06 PM, Joseph S. Myers wrote:
> On Tue, 10 Dec 2013, Will Newton wrote:
>> 2013-12-10 Will Newton <email@example.com>
>> * sysdeps/arm/__longjmp.S: Don't apply pointer encryption
>> to fp register.
>> * sysdeps/arm/setjmp.S: Likewise.
>> * sysdeps/arm/include/bits/setjmp.h (JMP_BUF_REGLIST): Add
>> fp to register list, remove a4.
>> * sysdeps/unix/sysv/linux/arm/sysdep.h: (PTR_MANGLE_LOAD):
>> New macro.
> OK, presuming you've tested this with the glibc testsuite.
Is it really true that ruby checks the FP?
I don't see such code? Can you please point it out?