This is the mail archive of the
mailing list for the glibc project.
Re: Ruby testsuite failures because of pointer mangling on 32-bit ARM?
- From: pinskia at gmail dot com
- To: David Miller <davem at davemloft dot net>
- Cc: "carlos at redhat dot com" <carlos at redhat dot com>, "will dot newton at linaro dot org" <will dot newton at linaro dot org>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Tue, 10 Dec 2013 11:57:03 -0800
- 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> <20131210 dot 141829 dot 170731967453318604 dot davem at davemloft dot net>
> On Dec 10, 2013, at 11:18 AM, David Miller <firstname.lastname@example.org> wrote:
> From: "Carlos O'Donell" <email@example.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.
Hmm, shouldn't ruby be using makecontext/restore context instead of setjmp/longjmp for this purpose? I think we should declare this as a bug in ruby.