Date: Wed, 19 Feb 2020 22:27:57 -0600 From: Zhihao Yuan <lichray@gmail.com> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: How much libc++ ABI changes FreeBSD can consume? Message-ID: <CAGsORuC7HVCCGRRLL92OQgLDAjTVRGmrMLsH=9Pn%2BsKgSKoQhg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi,
I'm sending this email because
a. FreeBSD has been stuck on libc++ V1 ABI
long enough. I would like to learn some details.
b. There is an ongoing discussion in the C++
standards committee talking about whether
the standard library should break ABI on a
regular basis.
Here are my questions:
1. Is FreeBSD waiting for libc++ V2 ABI to freeze?
If so, will FreeBSD switch to V2 ABI afterwards?
2. The pkgs are tagged with __FreeBSD_version,
is that enough to allow libc++ ABI to change
at every FreeBSD (major) release?
3. Is MFC required for libc++ updates? If so, how
does that affect ABI changes?
4. Is there any desire to make C++ ABI breakage
smoother by ultilzing mechanisms such as
Symbol.map?
Thanks,
--
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
_______________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGsORuC7HVCCGRRLL92OQgLDAjTVRGmrMLsH=9Pn%2BsKgSKoQhg>