diff options
| author | David Blaikie <dblaikie@gmail.com> | 2019-04-16 00:16:29 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2019-04-16 00:16:29 +0000 |
| commit | b068f92d94a5c42ff21bfdf29344c54e2688dac3 (patch) | |
| tree | 72d27cb21167a57aa5e71581817a1983c79611d5 /llvm/unittests/Support/CommandLineTest.cpp | |
| parent | 728780bfadfeae6dd9b7124d490be7d9f6c33de6 (diff) | |
| download | llvm-b068f92d94a5c42ff21bfdf29344c54e2688dac3.zip llvm-b068f92d94a5c42ff21bfdf29344c54e2688dac3.tar.gz llvm-b068f92d94a5c42ff21bfdf29344c54e2688dac3.tar.bz2 | |
DebugInfo: Default to standalone debug when tuning for LLDB
LLDB can't currently handle Clang's default (limit/no-standalone) DWARF,
so platforms that default to LLDB (Darwin) or anyone else manually
requesting LLDB tuning, should also get standalone DWARF.
That doesn't mean a user can't explicitly enable (because they have
other reasons to prefer standalone DWARF (such as that they're only
building half their application with debug info enabled, and half
without - or because they're tuning for GDB, but want to be able to use
it under LLDB too (this is the default on FreeBSD))) or disable (testing
LLDB fixes/improvements that handle no-standalone mode, building C code,
perhaps, which wouldn't have the LLDB<>no-standalone conflict, etc) the
feature regardless of the tuning.
llvm-svn: 358464
Diffstat (limited to 'llvm/unittests/Support/CommandLineTest.cpp')
0 files changed, 0 insertions, 0 deletions