forked from OSchip/llvm-project
96b1ed50e8
Since Split DWARF needs to name the actual .dwo file that is generated, it can't be known at the time the llvm::Module is produced as it may be merged with other Modules before the object is generated and that object may be generated with any name. By passing the Split DWARF file name when LLVM is producing object code the .dwo file name in the object file can match correctly. The support for Split DWARF for implicit modules remains the same - using metadata to store the dwo name and dwo id so that potentially multiple skeleton CUs referring to different dwo files can be generated from one llvm::Module. llvm-svn: 301062 |
||
|---|---|---|
| .. | ||
| line.test | ||
| lit.local.cfg | ||
| processes-relocations.ll | ||
| tls-fission.ll | ||
| tls.ll | ||