summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorBob Wilson <bob.wilson@apple.com>2017-02-14 19:06:43 +0000
committerBob Wilson <bob.wilson@apple.com>2017-02-14 19:06:43 +0000
commit4074b6b6864e2bef4206374400031c7d0c17cf4f (patch)
tree811d4ba7c0e6f29f8ce8ff74a15cf8b303100297 /clang/lib/Frontend/CompilerInvocation.cpp
parent8bd42a1a98377b717bfa3fae6efde4f72c18fea4 (diff)
downloadbcm5719-llvm-4074b6b6864e2bef4206374400031c7d0c17cf4f.tar.gz
bcm5719-llvm-4074b6b6864e2bef4206374400031c7d0c17cf4f.zip
allow migrating away from cmake option for LLVM_DISABLE_ABI_BREAKING_CHECKS_ENFORCING
In r288754, Mehdi added a cmake option to disable enforcement of the ABI breaking checks in the "abi-breaking.h" header. We used that when building Swift and it works, but I think it will be better to control this with a preprocessor macro instead of a cmake option. That will let us opt out of the enforcement more selectively. This change allows skipping the cmake setting if the existing preprocessor macro is already defined. My intention here is to make this change and get Swift to use it, and then after a few weeks, we can remove the cmake option. I want to stage it like that to be less disruptive. I'm not aware of anyone else using that cmake option. Mehdi had some initial concern about the impact of using a preprocessor macro when building with modules enabled. I don't think that will be a problem if we set the macro on the command line with a -D option in those contexts where we need to disable the enforcement of the checks. https://reviews.llvm.org/D29919 llvm-svn: 295090
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud