diff options
author | Reid Kleckner <rnk@google.com> | 2019-10-10 21:04:25 +0000 |
---|---|---|
committer | Reid Kleckner <rnk@google.com> | 2019-10-10 21:04:25 +0000 |
commit | 5e866e411caad4c4e17e7e0c67b06d28451e1bf2 (patch) | |
tree | 1ae51b6ec80724b28ad4c849dde12661289f3917 /lldb/packages/Python/lldbsuite/test/commands/expression/context-object-objc | |
parent | 53a53e63c85e53e70ea208a38d4efa9b90fb5f42 (diff) | |
download | bcm5719-llvm-5e866e411caad4c4e17e7e0c67b06d28451e1bf2.tar.gz bcm5719-llvm-5e866e411caad4c4e17e7e0c67b06d28451e1bf2.zip |
Add -fgnuc-version= to control __GNUC__ and other GCC macros
I noticed that compiling on Windows with -fno-ms-compatibility had the
side effect of defining __GNUC__, along with __GNUG__, __GXX_RTTI__, and
a number of other macros for GCC compatibility. This is undesirable and
causes Chromium to do things like mix __attribute__ and __declspec,
which doesn't work. We should have a positive language option to enable
GCC compatibility features so that we can experiment with
-fno-ms-compatibility on Windows. This change adds -fgnuc-version= to be
that option.
My issue aside, users have, for a long time, reported that __GNUC__
doesn't match their expectations in one way or another. We have
encouraged users to migrate code away from this macro, but new code
continues to be written assuming a GCC-only environment. There's really
nothing we can do to stop that. By adding this flag, we can allow them
to choose their own adventure with __GNUC__.
This overlaps a bit with the "GNUMode" language option from -std=gnu*.
The gnu language mode tends to enable non-conforming behaviors that we'd
rather not enable by default, but the we want to set things like
__GXX_RTTI__ by default, so I've kept these separate.
Helps address PR42817
Reviewed By: hans, nickdesaulniers, MaskRay
Differential Revision: https://reviews.llvm.org/D68055
llvm-svn: 374449
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/expression/context-object-objc')
0 files changed, 0 insertions, 0 deletions