diff options
| author | bors <bors@rust-lang.org> | 2020-03-13 16:10:20 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-03-13 16:10:20 +0000 |
| commit | d6072319a9fbeffea2ebe803ddaedbcf566ab5dd (patch) | |
| tree | 06038cab8de17d002d67d7be037bc1486042b21e /src/test/rustdoc-ui/coverage/json.rs | |
| parent | 54b7d21f59a363e53eb1c31d76b40af2ff99321c (diff) | |
| parent | cf929f77bffc9786fa7c15e75be7599cfc551225 (diff) | |
| download | rust-d6072319a9fbeffea2ebe803ddaedbcf566ab5dd.tar.gz rust-d6072319a9fbeffea2ebe803ddaedbcf566ab5dd.zip | |
Auto merge of #69155 - chrissimpkins:llvm-globals, r=eddyb
Add support for LLVM globals corresponding to miri allocations should be named alloc123 Adds support for this request from @eddyb in #69134: > That is, if -Zfewer-names is false (usually only because of --emit=llvm-ir), we should use the same name for LLVM globals we generate out of miri allocs as #67133 does in MIR output (allocN). > >This way, we can easily see the mapping between MIR and LLVM IR (and it shouldn't be any costlier for regular compilation, which would continue to use unnamed globals). r? @eddyb cc @oli-obk
Diffstat (limited to 'src/test/rustdoc-ui/coverage/json.rs')
0 files changed, 0 insertions, 0 deletions