diff options
author | Nico Weber <nicolasweber@gmx.de> | 2019-07-10 22:29:35 +0000 |
---|---|---|
committer | Nico Weber <nicolasweber@gmx.de> | 2019-07-10 22:29:35 +0000 |
commit | 101c1afdfd1c88f05da94c6fd317b489bb704f40 (patch) | |
tree | 700470aa28c63a3504ed88b179af98bdfc79b2c3 /lldb/packages/Python/lldbsuite/test | |
parent | d916f23b8303511cdea8e807c257c76edd6f62e2 (diff) | |
download | bcm5719-llvm-101c1afdfd1c88f05da94c6fd317b489bb704f40.tar.gz bcm5719-llvm-101c1afdfd1c88f05da94c6fd317b489bb704f40.zip |
driver: Don't warn about assembler flags being unused when not assembling
clang currently warns when passing flags for the assembler (e.g.
-Wa,-mbig-obj) to an invocation that doesn't run the assembler (e.g.
-E).
At first sight, that makes sense -- the flag really is unused. But many
other flags don't have an effect if no assembler runs (e.g.
-fno-integrated-as, -ffunction-sections, and many others), and those
currently don't warn. So this seems more like a side effect of how
CollectArgsForIntegratedAssembler() is implemented than like an
intentional feature.
Since it's a bit inconvenient when debugging builds and adding -E,
always call CollectArgsForIntegratedAssembler() to make sure assembler
args always get claimed. Currently, this affects only these flags:
-mincremental-linker-compatible, -mimplicit-it= (on ARM), -Wa, -Xassembler
It does have the side effect that assembler options now need to be valid
even if -E is passed. Previously, `-Wa,-mbig-obj` would error for
non-coff output only if the assembler ran, now it always errors. This
too makes assembler flags more consistent with all the other flags and
seems like a progression.
Fixes PR42066.
Differential Revision: https://reviews.llvm.org/D64527
llvm-svn: 365703
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions