Date: Wed, 22 Feb 2017 15:19:45 +0000 From: <Hartmut.Brandt@dlr.de> To: <dim@FreeBSD.org> Cc: <current@freebsd.org> Subject: RE: int128_t and uint128_t typeinfo Message-ID: <611243783F62AF48AFB07BC25FA4B1061CEECBB6@DLREXMBX01.intra.dlr.de> In-Reply-To: <3EBF6862-8DEC-4F96-9C95-78FEE5242A6C@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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]=20 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: >=20 > On 21 Feb 2017, at 13:48, Hartmut Brandt <hartmut.brandt@dlr.de> wrote: >>=20 >> it looks like the typeinfo for __int128_t and __uint128_t is missing fro= m our dynamically linked libcxxrt. ... > * We also need to add the typeinfo for __u?int128_t * and __u?int128_t =20 > const * > * Maybe these should be under the CXXABI_2.0 version, since that is =20 > where newer libstdc++ places them > * Maybe these should be dependent on whether the architecture supports > 128 bit integers at all >=20 > I need to think a bit on the above, then I'll commit a fix. Okay, can you please try r314061? -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?611243783F62AF48AFB07BC25FA4B1061CEECBB6>