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: David Miller <davem at davemloft dot net>
- To: carlos at redhat dot com
- Cc: will dot newton at linaro dot org, libc-alpha at sourceware dot org
- Date: Tue, 10 Dec 2013 14:18:29 -0500 (EST)
- Subject: Re: Ruby testsuite failures because of pointer mangling on 32-bit ARM?
- Authentication-results: sourceware.org; auth=none
- References: <CANu=DmgWNhyxq9vE37bvvD=PrDrfi0Y+eAMv0i2KZPxaEnEOxw at mail dot gmail dot com> <CANu=Dmi=8JB-=2M_SccqJtAo6Ueny37D-JE0jaG1ErqrNLQ3qQ at mail dot gmail dot com> <52A75D39 dot 6010506 at redhat dot com>
From: "Carlos O'Donell" <carlos@redhat.com>
Date: Tue, 10 Dec 2013 13:28:09 -0500
> If it's actually looking into the jmpbuf we can claim undefined
> behaviour and shutdown the bug as a ruby issue.
>
> I haven't seen any bespoke per-target code in Ruby that actually
> looks into the jmpbuf, have you?
There is a lot of tricky stuff that ruby does wrt. stack frames.
It copies thread stack blocks around, and even has specialized code
to handle sparc register windows and IA64 register stacks.
Take a look at cont_save_machine_stack in cont.c for example.