about summary refs log tree commit diff
path: root/compiler/rustc_driver/src
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-10-25 04:57:51 +0000
committerbors <bors@rust-lang.org>2022-10-25 04:57:51 +0000
commit31d754a1dfba4d091a05589459708f286d5a231e (patch)
tree25ea743dd19ec2f0eb44d53ee688235c2cb614c8 /compiler/rustc_driver/src
parentf2702e922ba31e49d6167f5651d4545646dcf22d (diff)
parent3a1ef50b34d3c88ddc423411be4521499cf9def5 (diff)
downloadrust-31d754a1dfba4d091a05589459708f286d5a231e.tar.gz
rust-31d754a1dfba4d091a05589459708f286d5a231e.zip
Auto merge of #102988 - dpaoliello:inlinerawdylib, r=dpaoliello
Support raw-dylib functions being used inside inlined functions

Fixes #102714

Issue Details:
When generating the import library for `raw-dylib` symbols, we currently only use the functions and variables declared within the current crate. This works fine if all crates are static libraries or `rlib`s as the generated import library will be contained in the static library or `rlib` itself, but if a dependency is a dynamic library AND the use of a `raw-dylib` function or variable is inlined or part of a generic instantiation then the current crate won't see its dependency's import library and so linking will fail.

Fix Details:
Instead, when we generate the import library for a `dylib` or `bin` crate, we will now generate it for the symbols both for the current crate and all upstream crates. We do this in two steps so that the import library for the current crate is passed into the linker first, thus it is preferred if there are any ambiguous symbols.
Diffstat (limited to 'compiler/rustc_driver/src')
0 files changed, 0 insertions, 0 deletions