Date: Wed, 22 Feb 2017 19:48:56 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Hartmut.Brandt@dlr.de Cc: current@freebsd.org Subject: Re: int128_t and uint128_t typeinfo Message-ID: <201471EF-D383-49C0-B03B-64B91BAA4F0A@FreeBSD.org> In-Reply-To: <611243783F62AF48AFB07BC25FA4B1061CEECBB6@DLREXMBX01.intra.dlr.de> References: <alpine.BSF.2.20.1702211347050.82742@KNOP-BEAGLE.kn.op.dlr.de> <54594A33-C1DE-4491-8AD2-04E354EC5FAE@FreeBSD.org> <3EBF6862-8DEC-4F96-9C95-78FEE5242A6C@FreeBSD.org> <611243783F62AF48AFB07BC25FA4B1061CEECBB6@DLREXMBX01.intra.dlr.de>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
I had to commit a follow-up fix in r314104: when C++ names are used in
the version script, they have to be surrounded by an extern "C++" {}
block, otherwise the symbols end up as locals in the final library, and
thus get stripped out of the installed version.
-Dimitry
On 22 Feb 2017, at 16:19, Hartmut.Brandt@dlr.de wrote:
>
> Looks like they are still not there. I've rebuilt world.
>
> nm -D -C /usr/lib/libcxxrt.so | grep 128
>
> should show me the symbols, right? It does not.
>
> harti
>
> -----Original Message-----
> From: Dimitry Andric [mailto:dim@FreeBSD.org]
> Sent: Tuesday, February 21, 2017 10:52 PM
> To: Brandt, Hartmut
> Cc: current@freebsd.org
> Subject: Re: int128_t and uint128_t typeinfo
>
> On 21 Feb 2017, at 18:26, Dimitry Andric <dim@FreeBSD.org> wrote:
>>
>> On 21 Feb 2017, at 13:48, Hartmut Brandt <hartmut.brandt@dlr.de> wrote:
>>>
>>> it looks like the typeinfo for __int128_t and __uint128_t is missing from our dynamically linked libcxxrt.
> ...
>> * We also need to add the typeinfo for __u?int128_t * and __u?int128_t
>> const *
>> * Maybe these should be under the CXXABI_2.0 version, since that is
>> where newer libstdc++ places them
>> * Maybe these should be dependent on whether the architecture supports
>> 128 bit integers at all
>>
>> I need to think a bit on the above, then I'll commit a fix.
>
> Okay, can you please try r314061?
>
> -Dimitry
>
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
iEYEARECAAYFAlit3SIACgkQsF6jCi4glqOqaACfbOUwrO/ovhz8Dbwca4e1THTS
/UAAn0WRQeDkuvMK/tUaKADj5OJQNvpE
=UqhR
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201471EF-D383-49C0-B03B-64B91BAA4F0A>