Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Dec 2021 21:07:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 215193] libc++ and libcxxrt: convert to a private library
Message-ID:  <bug-215193-29464-FMJAicmCl8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215193-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-215193-29464@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215193

Mark Millard <marklmi26-fbsd@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marklmi26-fbsd@yahoo.com

--- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to David Chisnall from comment #2)

For reference:

https://releases.llvm.org/13.0.0/projects/libcxx/docs/DesignDocs/ABIVersion=
ing.html

reports .  . .

QUOTE
Libc++ aims to preserve a stable ABI to avoid subtle bugs when code built u=
nder
the old ABI is linked with code built under the new ABI. At the same time,
libc++ wants to make ABI-breaking improvements and bugfixes in scenarios wh=
ere
the user doesn=E2=80=99t mind ABI breaks.

To support both cases, libc++ allows specifying an ABI version at build tim=
e.
The version is defined with CMake option LIBCXX_ABI_VERSION. Currently
supported values are 1 (the stable default) and 2 (the unstable =E2=80=9Cne=
xt=E2=80=9D
version). At some point =E2=80=9CABI version 2=E2=80=9D will be frozen and =
new ABI-breaking
changes will start being applied to version 3; but this has not happened ye=
t.

To always use the most cutting-edge, most unstable ABI (which is currently 2
but at some point will become 3), set the CMake option LIBCXX_ABI_UNSTABLE.

Internally, each ABI-changing feature is placed under its own C++ macro,
_LIBCPP_ABI_XXX. These macros=E2=80=99 definitions are controlled by the C+=
+ macro
_LIBCPP_ABI_VERSION, which is controlled by the LIBCXX_ABI_VERSION set at b=
uild
time. Libc++ does not intend users to interact with these C++ macros direct=
ly.
END QUOTE

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215193-29464-FMJAicmCl8>