[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150723170234.GE382@port70.net>
Date: Thu, 23 Jul 2015 19:02:34 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: implement stdatomic.h library interface
* Joakim Sindholt <opensource@...sha.com> [2015-07-23 18:32:26 +0200]:
> On Thu, 2015-07-23 at 17:04 +0200, Jens Gustedt wrote:
> > Am Donnerstag, den 23.07.2015, 16:42 +0200 schrieb Szabolcs Nagy:
> > > this IFUNC elf extension is not supported by musl now so
> > > loading a shared object with such symbols will fail
> > > (not sure what happens with static linking) so you have
> > > to build a musl specific toolchain now to use libatomic.
> >
> > Static linking seems to work fine.
>
> Then you're not hitting the fallback symbols. They will initially be
> NULL and you should get SIGSEGV. At least this was the result I saw when
> trying to use ifunc resolver in a static binary with musl.
these are the ifunc symbols in current gcc libatomic on x86_64:
$ nm libatomic.a |grep ' i '
0000000000000040 i __atomic_load_16
0000000000000030 i __atomic_store_16
0000000000000070 i __atomic_compare_exchange_16
0000000000000050 i __atomic_exchange_16
00000000000000c0 i __atomic_add_fetch_16
00000000000000a0 i __atomic_fetch_add_16
00000000000000b0 i __atomic_fetch_sub_16
00000000000000d0 i __atomic_sub_fetch_16
00000000000000b0 i __atomic_and_fetch_16
0000000000000090 i __atomic_fetch_and_16
0000000000000090 i __atomic_fetch_or_16
00000000000000b0 i __atomic_or_fetch_16
0000000000000090 i __atomic_fetch_xor_16
00000000000000b0 i __atomic_xor_fetch_16
0000000000000090 i __atomic_fetch_nand_16
00000000000000b0 i __atomic_nand_fetch_16
0000000000000010 i __atomic_test_and_set_16
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.
