diff options
| author | bors <bors@rust-lang.org> | 2021-05-14 12:58:58 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-05-14 12:58:58 +0000 |
| commit | a5da29cf8f45f831e52c1e027eea73f3937c810d (patch) | |
| tree | 9a537ddc165cbef6fef0c0a86f1cf03f71120f96 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | d342a3490b6f85f5bec80a7b90a576e5044719aa (diff) | |
| parent | 62f64af43051fde2b9e643a0f5f06cf88e602a59 (diff) | |
| download | rust-a5da29cf8f45f831e52c1e027eea73f3937c810d.tar.gz rust-a5da29cf8f45f831e52c1e027eea73f3937c810d.zip | |
Auto merge of #83640 - bjorn3:shared_metadata_reader, r=nagisa
Use the object crate for metadata reading This allows sharing the metadata reader between cg_llvm, cg_clif and other codegen backends. This is not currently useful for rlib reading with cg_spirv ([rust-gpu](https://github.com/EmbarkStudios/rust-gpu/)) as it uses tar rather than ar as .rlib format, but it is useful for dylib reading required for loading proc macros. (cc `@eddyb)` The object crate is already trusted as dependency of libstd through backtrace. As far as I know it supports reading all object file formats used by targets for which we support rust dylibs with crate metadata, but I am not certain. If this happens to not be the case, I could keep using LLVM for reading dylib metadata. Marked as WIP for a perf run and as it is based on #83637.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions