[libcxx-dev] Stabilizing libc++'s ABI v2
Eric Fiselier via libcxx-dev
libcxx-dev at lists.llvm.org
Thu Mar 21 02:54:16 PDT 2019
libc++ should support only three ABI versions at once: deprecated, stable,
Making v2 stable means deprecating v1. The time between deprecation and
limits how often we can cut a new ABI.
How long should we support the deprecated ABI's for?
On Wed, Mar 20, 2019 at 3:47 PM Louis Dionne via libcxx-dev <
libcxx-dev at lists.llvm.org> wrote:
> On Mar 20, 2019, at 14:02, Mikhail Maltsev <Mikhail.Maltsev at arm.com>
> On 3/20/19 5:24 PM, Marshall Clow via libcxx-dev wrote:
> On Tue, Mar 19, 2019 at 1:10 PM Louis Dionne via libcxx-dev
> <libcxx-dev at lists.llvm.org <mailto:libcxx-dev at lists.llvm.org
> <libcxx-dev at lists.llvm.org>>> wrote:
> I'd like to know whether folks currently have breaking changes planned
> the version 2 ABI of libc++. Are we aware of improvements that would
> breaking the ABI and that we have not implemented yet?
> I have a note to fix XXX::set_value to use call_once when I can break ABI,
> so I
> should do that first.
> You also mentioned some <regex>-related changes:
> Right, those two items are exactly the kind of thing I was thinking about.
> Let's implement those and put them behind ABI macros just so we don't
> forget. When we are ready to stabilize the ABI we won't miss those changes.
> libcxx-dev mailing list
> libcxx-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libcxx-dev