about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-07-24 05:13:39 +0000
committerbors <bors@rust-lang.org>2015-07-24 05:13:39 +0000
commitc9ef1a5c19b8f9a254b0fb0b79a3bebf0722a9ce (patch)
treee14617f6387d8cb9086afc91ed1677050e7f624f /src/libstd/sys/unix/stack_overflow.rs
parent68e0d13bfdcb83bfd4232ad33a1a7e271bff8994 (diff)
parenta0efd3a3d99a98e3399a4f07abe6a67cf0660335 (diff)
downloadrust-c9ef1a5c19b8f9a254b0fb0b79a3bebf0722a9ce.tar.gz
rust-c9ef1a5c19b8f9a254b0fb0b79a3bebf0722a9ce.zip
Auto merge of #27208 - alexcrichton:msvc-less-dllimport, r=brson
Currently you can hit a link error on MSVC by only referencing static items from
a crate (no functions for example) and then link to the crate statically (as all
Rust crates do 99% of the time). A detailed investigation can be found [on
github][details], but the tl;dr is that we need to stop applying dllimport so
aggressively.

This commit alters the application of dllimport on constants to only cases where
the crate the constant originated from will be linked as a dylib in some output
crate type. That way if we're just linking rlibs (like the motivation for this
issue) we won't use dllimport. For the compiler, however, (which has lots of
dylibs) we'll use dllimport.

[details]: https://github.com/rust-lang/rust/issues/26591#issuecomment-123513631

cc #26591
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions