aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineModuleInfoImpls.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne.2@gmail.com>2022-05-16 10:04:33 -0400
committerLouis Dionne <ldionne.2@gmail.com>2022-05-16 15:23:43 -0400
commitefcee4b06d2f8ee6c79dd893b702f073593d5823 (patch)
tree33134f4a227b34bd7ad1f46394bab56923a2bd37 /llvm/lib/CodeGen/MachineModuleInfoImpls.cpp
parentd4aacc1a013e9de4011adb051cdcae1ae6fc9baf (diff)
downloadllvm-efcee4b06d2f8ee6c79dd893b702f073593d5823.zip
llvm-efcee4b06d2f8ee6c79dd893b702f073593d5823.tar.gz
llvm-efcee4b06d2f8ee6c79dd893b702f073593d5823.tar.bz2
[libc++] Remove the legacy LIBCXX_LIBCPPABI_VERSION option
I think this notion of libc++abi's version was relevant a long time ago on Apple platforms when we were using a Xcode project to build the library. As part of moving Apple's build to CMake, D59489 made it possible to specify the "ABI version" of libc++abi in use. However, it's not possible to build libc++abi with that old ABI anymore and we don't need the ability to link against that version from libc++ anymore. Hence, we can clean this up and stop falsely pretending that libc++abi has more than one ABI version. Differential Revision: https://reviews.llvm.org/D125687
Diffstat (limited to 'llvm/lib/CodeGen/MachineModuleInfoImpls.cpp')
0 files changed, 0 insertions, 0 deletions