[libcxx-dev] Stabilizing libc++'s ABI v2

[Duncan Exon Smith via libcxx-dev]

We don't talk publicly about any internal plans, but any vendor that supports back-deployment to old OS releases couldn't migrate off v1 until a very long time after shipping v2.

> On 2019 Mar  19, at 22:47, Eric Fiselier <eric at efcs.ca> wrote:
> 
> Does Apple have a plan to migrate off ABI v1?
> 
> /Eric
> 
> On Tue, Mar 19, 2019 at 5:33 PM Duncan Exon Smith via libcxx-dev <libcxx-dev at lists.llvm.org <mailto:libcxx-dev at lists.llvm.org>> wrote:
> 
> > On 2019 Mar  19, at 13:10, Louis Dionne via libcxx-dev <libcxx-dev at lists.llvm.org <mailto:libcxx-dev at lists.llvm.org>> wrote:
> > 
> > I'd like to know whether folks currently have breaking changes planned for the version 2 ABI of libc++. Are we aware of improvements that would require breaking the ABI and that we have not implemented yet?
> 
> The one I'm aware of is a compressed mangling for versioning namespaces:
>   https://github.com/itanium-cxx-abi/cxx-abi/pull/69 <https://github.com/itanium-cxx-abi/cxx-abi/pull/69>
> 
> 
> _______________________________________________
> libcxx-dev mailing list
> libcxx-dev at lists.llvm.org <mailto:libcxx-dev at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev <https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/libcxx-dev/attachments/20190320/90f16040/attachment.html>