diff options
| author | bors <bors@rust-lang.org> | 2022-07-21 10:13:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-07-21 10:13:59 +0000 |
| commit | 74f600b990240556c9a355c5d03293a10934bd1b (patch) | |
| tree | 4b12cbd785b255a340b0ff57ec22d9e49af78a5c /compiler/rustc_codegen_gcc | |
| parent | ceeb5ade201e4181c6d5df2ba96ae5fb2193aadc (diff) | |
| parent | 724c91234dd49b88d70ebead406d09105695c3e5 (diff) | |
| download | rust-74f600b990240556c9a355c5d03293a10934bd1b.tar.gz rust-74f600b990240556c9a355c5d03293a10934bd1b.zip | |
Auto merge of #98162 - nextsilicon:support_lto_embed_bitcode, r=davidtwco
Allow to disable thinLTO buffer to support lto-embed-bitcode lld feature Hello This change is to fix issue (https://github.com/rust-lang/rust/issues/84395) in which passing "-lto-embed-bitcode=optimized" to lld when linking rust code via linker-plugin-lto doesn't produce the expected result. Instead of emitting a single unified module into a llvmbc section of the linked elf, it emits multiple submodules. This is caused because rustc emits the BC modules after running llvm `createWriteThinLTOBitcodePass` pass. Which in turn triggers a thinLTO linkage and causes the said issue. This patch allows via compiler flag (-Cemit-thin-lto=<bool>) to select between running `createWriteThinLTOBitcodePass` and `createBitcodeWriterPass`. Note this pattern of selecting between those 2 passes is common inside of LLVM code. The default is to match the old behavior.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions