aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/Program.cpp
diff options
context:
space:
mode:
authorMartin Storsjö <martin@martin.st>2020-06-13 22:29:52 +0300
committerMartin Storsjö <martin@martin.st>2020-06-17 09:37:07 +0300
commit7b3fe969927731c69ba4d8a428442e1e191f49b5 (patch)
tree885fe4924d6e83d3e1f3a457d66921040921d3fd /llvm/lib/Support/Program.cpp
parentbeeed368b60252178f66ab117d8a96ecdc35f60e (diff)
downloadllvm-7b3fe969927731c69ba4d8a428442e1e191f49b5.zip
llvm-7b3fe969927731c69ba4d8a428442e1e191f49b5.tar.gz
llvm-7b3fe969927731c69ba4d8a428442e1e191f49b5.tar.bz2
[clang] Don't emit warn_cxx_ms_struct when MSBitfields is enabled globally
This diagnostic (which defaults to an error, added in 95833f33bda6c92e746e0b0007b69c2c30bfc693) was intended to clearly point out cases where the C++ ABI won't match the Microsoft C++ ABI, for cases when this is enabled via a pragma over a region of code. The MSVC compatible struct layout feature can also be enabled via a compiler option (-mms-bitfields). If enabled that way, one essentially can't compile any C++ code unless also building with -Wno-incompatible-ms-struct (which GCC doesn't support, and projects developed with GCC aren't setting). For the MinGW target, it's expected that the C++ ABI won't match the MSVC one, if this option is used for getting the struct layout to match MSVC. Differential Revision: https://reviews.llvm.org/D81794
Diffstat (limited to 'llvm/lib/Support/Program.cpp')
0 files changed, 0 insertions, 0 deletions