Consider building libc++ with _LIBCPP_ABI_UNSTABLE |
||||
Issue descriptionOn Linux and Android, we don't care about libc++ ABI stability. If we define _LIBCPP_ABI_UNSTABLE we get a bunch of presumably beneficial changes that break ABI (https://github.com/llvm-mirror/libcxx/blob/master/include/__config#L52). We might want to turn that on. We might want to wait until we use the same libc++ on Android on Linux ( issue 747675 ) before doing that, to keep the config matrix a bit smaller.
,
Nov 16 2017
,
May 8 2018
,
Dec 20
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0f0b0a857e911b152d694c20852b2424ce7868da commit 0f0b0a857e911b152d694c20852b2424ce7868da Author: Tom Anderson <thomasanderson@chromium.org> Date: Thu Dec 20 02:24:57 2018 Build with _LIBCPP_ABI_UNSTABLE BUG= 747676 R=thakis Change-Id: Ib3e8d058b380764ee55de77b5993b3ecbf7137e9 Reviewed-on: https://chromium-review.googlesource.com/c/1379066 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#618079} [modify] https://crrev.com/0f0b0a857e911b152d694c20852b2424ce7868da/build/config/posix/BUILD.gn [modify] https://crrev.com/0f0b0a857e911b152d694c20852b2424ce7868da/build/config/win/BUILD.gn
,
Dec 20
|
||||
►
Sign in to add a comment |
||||
Comment 1 by thomasanderson@chromium.org
, Nov 8 2017