diff options
author | Raphael Isemann <teemperor@gmail.com> | 2023-02-14 22:55:46 +0100 |
---|---|---|
committer | Raphael Isemann <teemperor@gmail.com> | 2023-02-14 23:20:56 +0100 |
commit | 9f3a3e1f3f9767ae52c492d20d63f65e82319ed2 (patch) | |
tree | 0dd1911eb39410cb2a637afb44bcddfa190f169a /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
parent | 20cdf7c7066794805546bd33803befb24207ad85 (diff) | |
download | llvm-9f3a3e1f3f9767ae52c492d20d63f65e82319ed2.zip llvm-9f3a3e1f3f9767ae52c492d20d63f65e82319ed2.tar.gz llvm-9f3a3e1f3f9767ae52c492d20d63f65e82319ed2.tar.bz2 |
[lldb] Disable macro redefinition warnings in expression wrapper
GCC emits macro definitions into debug info when compiling with `-g3`. LLDB is
translating this information into `#define` directives which are injected into
the source code of user expressions. While this mechanism itself works fine,
it can lead to spurious "... macro redefined" warnings when the defined macro
is also a builtin Clang macro:
```
warning: <lldb wrapper prefix>:46:9: '__VERSION__' macro redefined
^
<built-in>:19:9: previous definition is here
[repeated about a 100 more times for every builtin macro]
```
This patch just disables the diagnostic when parsing LLDB's generated list of
macros definitions.
Reviewed By: Michael137
Differential Revision: https://reviews.llvm.org/D139740
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions