From owner-freebsd-toolchain@freebsd.org  Sat Jul 29 18:17:31 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF148DC8414
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Sat, 29 Jul 2017 18:17:31 +0000 (UTC)
 (envelope-from theraven@FreeBSD.org)
Received: from theravensnest.org (xvm-110-62.dc2.ghst.net [46.226.110.62])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "theravensnest.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 50E00731C0;
 Sat, 29 Jul 2017 18:17:30 +0000 (UTC)
 (envelope-from theraven@FreeBSD.org)
Received: from [192.168.1.65] (host86-138-54-151.range86-138.btcentralplus.com
 [86.138.54.151]) (authenticated bits=0)
 by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id v6TIHLIg031362
 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 29 Jul 2017 18:17:21 GMT (envelope-from theraven@FreeBSD.org)
X-Authentication-Warning: d60e724c-75b0-4b63-9702-f4a9d2bf6793: Host
 host86-138-54-151.range86-138.btcentralplus.com [86.138.54.151] claimed to be
 [192.168.1.65]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: libcxxrt seems to lack some features that are present in libc++abi
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <3F666806-E4A0-4FD0-915E-16767213A432@FreeBSD.org>
Date: Sat, 29 Jul 2017 19:17:15 +0100
Cc: Oleg Lelchuk <oleglelchuk@gmail.com>,
 FreeBSD Toolchain <freebsd-toolchain@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A9341F1-9B6B-4FEC-B2C9-BAC72A86E013@FreeBSD.org>
References: <CA+GqWgsvDCfU2KvF6Hd3cCKGa6MA62-6KtGJ5LNGJrBB+_T0hg@mail.gmail.com>
 <3F666806-E4A0-4FD0-915E-16767213A432@FreeBSD.org>
To: Dimitry Andric <dim@FreeBSD.org>
X-Mailer: Apple Mail (2.3273)
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2017 18:17:31 -0000

On 29 Jul 2017, at 17:55, Dimitry Andric <dim@FreeBSD.org> wrote:
>=20
> The demangler in libcxxrt is indeed rather old, and we should replace =
it
> with something newer.  I'm not sure if the demangler of libc++abi is =
the
> right one yet, since upstream seems to still be discussing which of
> their three (or thereabouts) demanglers should be *the* LLVM =
demangler.
>=20
> Ed, IIRC you had some looks at this before, do you have any =
preference?

I spoke to the ELF Toolchain maintainer a little while ago and pointed =
out that the demangler that we got from there lacked some features.  =
Maybe we can persuade him to add support for r-value references?

Ideally, I=E2=80=99d like to make the one in libcxxrt a weak symbol and =
ship the LLVM one in a separate library - it=E2=80=99s very big, so =
linking it into things like devd would be silly, but anything that=E2=80=99=
s dynamically linking libc++ would probably not notice the increase in =
code size.

David