[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEg67Gnsu9p_oaOXtFKubdWZi8KEP5mZzuJY5NkjvgGPNVSnew@mail.gmail.com>
Date: Mon, 21 Oct 2019 16:51:20 +1100
From: Patrick Oppenlander <patrick.oppenlander@...il.com>
To: musl@...ts.openwall.com
Subject: Re: another armv7-m exception handling problem
On Mon, Oct 21, 2019 at 4:38 PM Rich Felker <dalias@...c.org> wrote:
>
> On Mon, Oct 21, 2019 at 04:34:07PM +1100, Patrick Oppenlander wrote:
> > On Mon, Oct 21, 2019 at 4:20 PM Rich Felker <dalias@...c.org> wrote:
> > >
> > > On Mon, Oct 21, 2019 at 01:04:11AM -0400, Rich Felker wrote:
> > > >
> > > > OK, this is almost surely a bug in the tooling -- a weak reference has
> > > > to use a GOT slot in PIC since it might be undefined and need to
> > > > evaluate to 0, and the GOT slot should not have a relocation on it if
> > > > it ends up evaluating to 0. Pretty sure it's ld's fault.
> >
> > Makes sense. Should I report to the binutils guys?
>
> I think so, but it would probably be worth determining whether it's
> arm-specific or more general first so that the report gets to the
> right ppl. I can try it on some other archs tomorrow.
Here's the ones I have on hand:
% aarch64-linux-musleabi-gcc -static weakref2.c -o aarch64
% arm-linux-musleabi-gcc -static weakref2.c -o arm
% armv7m-linux-musleabi-gcc -static weakref2.c -o armv7m
% x86_64-linux-musl-gcc -static weakref2.c -o x86_64
% ./aarch64
0
% ./arm
0
% ./armv7m
0xfffdb000
% ./x86_64
0
End of day for me too.
Patrick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
