diff options
| author | Fangrui Song <maskray@google.com> | 2020-04-14 14:17:29 -0700 |
|---|---|---|
| committer | Fangrui Song <maskray@google.com> | 2020-04-15 08:00:50 -0700 |
| commit | cd5d5ce235081005173566c99c592550021de058 (patch) | |
| tree | b7aa778603341d723960d11381c53d135e0050dc /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | 7a6aaf9b23d6ac2fb8c11c00c73e55c0bc7aa2f0 (diff) | |
| download | llvm-cd5d5ce235081005173566c99c592550021de058.zip llvm-cd5d5ce235081005173566c99c592550021de058.tar.gz llvm-cd5d5ce235081005173566c99c592550021de058.tar.bz2 | |
[ELF] Refactor the way we handle -plugin-opt= (GCC collect2 or clang LTO related options)
GCC collect2 passes several options to the linker even if LTO is not used
(note, lld does not support GCC LTO). The lto-wrapper may be a relative
path (especially during development, when gcc is in a build directory), e.g.
-plugin-opt=relative/path/to/lto-wrapper
We need to ignore such options, which are currently interpreted by
cl::ParseCommandLineOptions() and will fail with `error: --plugin-opt: ld.lld: Unknown command line argument 'relative/path/to/lto-wrapper'`
because the path is apparently not an option registered by an `llvm::cl::opt`.
See lto-plugin-ignore.s for how we interpret various -plugin-opt= options now.
Reviewed By: grimar, tejohnson
Differential Revision: https://reviews.llvm.org/D78158
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions