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: Andrew Pinski <pinskia at gmail dot com>
- To: David Miller <davem at davemloft dot net>
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, Will Newton <will dot newton at linaro dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 10 Dec 2013 17:13:30 -0800
- Subject: Re: Ruby testsuite failures because of pointer mangling on 32-bit ARM?
- Authentication-results: sourceware.org; auth=none
- References: <52A75D39 dot 6010506 at redhat dot com> <20131210 dot 141829 dot 170731967453318604 dot davem at davemloft dot net> <186C0AD8-CFA3-4EE1-AB18-1158E32F1F1B at gmail dot com> <20131210 dot 173622 dot 2212833574581899559 dot davem at davemloft dot net>
On Tue, Dec 10, 2013 at 2:36 PM, David Miller <davem@davemloft.net> wrote:
> From: pinskia@gmail.com
> Date: Tue, 10 Dec 2013 11:57:03 -0800
>
>> 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.
>
> I honestly think that what Ruby is doing is quite reasonable.
How so, jmp_buf is supposed to be an opaque structure. If a program
depends on the context of an opaque structure, then it is a bug in the
program rather than the library which changes what the opaque
structure contains. This is the whole point of using
makecontext/restorecontext instead, those structures are not designed
to be opaque.
Thanks,
Andrew Pinski