summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2018-08-16 17:34:31 +0000
committerReid Kleckner <rnk@google.com>2018-08-16 17:34:31 +0000
commitbd5d71229db6c6c4f2446229de9b0e930b7f6be9 (patch)
treec7bf8f171a38310c196d7ad99ad68cd029d52850 /lldb/packages/Python/lldbsuite/test/configuration.py
parenteb189a0ef77b6399b822de2a4e8847e573c50702 (diff)
downloadbcm5719-llvm-bd5d71229db6c6c4f2446229de9b0e930b7f6be9.tar.gz
bcm5719-llvm-bd5d71229db6c6c4f2446229de9b0e930b7f6be9.zip
[codeview] Use push_macro to avoid conflicts instead of a prefix
Summary: This prefix was added in r333421, and it changed our dumper output to say things like "CVRegEAX" instead of just "EAX". That's a functional change that I'd rather avoid. I tested GCC, Clang, and MSVC, and all of them support #pragma push_macro. They don't issue warnings whem the macro is not defined either. I don't have a Mac so I can't test the real termios.h header, but I looked at the termios.h sources online and looked for other conflicts. I saw only the CR* macros, so those are the ones we work around. Reviewers: zturner, JDevlieghere Subscribers: hiraditya, llvm-commits Differential Revision: https://reviews.llvm.org/D50851 llvm-svn: 339907
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud