aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorDavid Blaikie <dblaikie@gmail.com>2017-04-28 20:50:25 +0000
committerDavid Blaikie <dblaikie@gmail.com>2017-04-28 20:50:25 +0000
commit9bb296cb05284fedf407dd1424bceb214991f5f2 (patch)
treef7f1835e4f9bef1b77add446ff52fdda7b0e28f5 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent3012b371fd1163ef6d269209bfd8e8dfbae59379 (diff)
downloadllvm-9bb296cb05284fedf407dd1424bceb214991f5f2.zip
llvm-9bb296cb05284fedf407dd1424bceb214991f5f2.tar.gz
llvm-9bb296cb05284fedf407dd1424bceb214991f5f2.tar.bz2
Enable -fno-split-dwarf-inlining even when -gsplit-dwarf isn't specified.
Since -gsplit-dwarf is specified on a backend compile (in ThinLTO parlance) it isn't passed during the frontend compile (because no ELF object/dwo file is produced then), yet the -fno-split-dwarf-inlining value needs to be encoded in the LLVM DebugInfo metadata to have effect... So let it be specified & it'll be silently ignored if -gsplit-dwarf isn't used in the end, otherwise it'll be used on a per-cu basis depending on where it's specified in the frontend compile actions. llvm-svn: 301684
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions