summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-exegesis/lib/Uops.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne@apple.com>2018-09-26 08:24:51 +0000
committerLouis Dionne <ldionne@apple.com>2018-09-26 08:24:51 +0000
commitf9a52903efa5a32e1d2914d26dbee77a25c7c2a8 (patch)
tree20f3f94893561728aa9a2d925217e1180e85e026 /llvm/tools/llvm-exegesis/lib/Uops.cpp
parent95aae4c59d22d5e5583d4dc7a2c92b3ed37591ca (diff)
downloadbcm5719-llvm-f9a52903efa5a32e1d2914d26dbee77a25c7c2a8.tar.gz
bcm5719-llvm-f9a52903efa5a32e1d2914d26dbee77a25c7c2a8.zip
[libc++] Remove Fuchsia-specific knowledge to pick the ABI version
Summary: The ABI version used by libc++ is a configuration option just like any other configuration option. It is a knob that can be used by vendors to customize the libc++ that they ship. As such, we should not be hardcoding vendor-specific configuration choices in libc++. When building libc++ for Fuchsia, Fuchsia's build scripts should simply define the libc++ ABI version to 2 -- this will result in the _LIBCPP_ABI_VERSION macro being defined in the __config header that is generated when libc++ is built and installed, which is the correct way to customize libc++'s behavior for specific vendors. Reviewers: phosek, EricWF Subscribers: mgorny, christof, dexonsmith, cfe-commits, libcxx-commits Differential Revision: https://reviews.llvm.org/D52397 llvm-svn: 343079
Diffstat (limited to 'llvm/tools/llvm-exegesis/lib/Uops.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud