From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
To: musl@lists.openwall.com
Subject: Re: another armv7-m exception handling problem
Date: Mon, 21 Oct 2019 16:51:20 +1100 [thread overview]
Message-ID: <CAEg67Gnsu9p_oaOXtFKubdWZi8KEP5mZzuJY5NkjvgGPNVSnew@mail.gmail.com> (raw)
In-Reply-To: <20191021053829.GG16318@brightrain.aerifal.cx>
On Mon, Oct 21, 2019 at 4:38 PM Rich Felker <dalias@libc.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@libc.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
next prev parent reply other threads:[~2019-10-21 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 4:43 Patrick Oppenlander
2019-10-21 5:04 ` Rich Felker
2019-10-21 5:20 ` Rich Felker
2019-10-21 5:34 ` Patrick Oppenlander
2019-10-21 5:38 ` Rich Felker
2019-10-21 5:51 ` Patrick Oppenlander [this message]
2019-10-21 18:09 ` Szabolcs Nagy
2019-10-21 19:03 ` Rich Felker
2019-10-21 19:08 ` Szabolcs Nagy
2019-10-21 19:29 ` Rich Felker
2020-01-10 10:22 ` Szabolcs Nagy
2020-01-11 6:20 ` Patrick Oppenlander
2019-10-21 21:17 ` Patrick Oppenlander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEg67Gnsu9p_oaOXtFKubdWZi8KEP5mZzuJY5NkjvgGPNVSnew@mail.gmail.com \
--to=patrick.oppenlander@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).