rust/tests/ui/linkage-attr/issue-12133-3.rs

//@ run-pass
//@ aux-build:issue-12133-rlib.rs
//@ aux-build:issue-12133-dylib.rs
//@ aux-build:issue-12133-dylib2.rs
//@ ignore-wasm32 no dylib support
//@ ignore-musl
//@ needs-dynamic-linking

//@ pretty-expanded FIXME #23616

extern crate issue_12133_dylib2 as other;

fn main() {}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`//@ run-pass`
Tweak how preference factors into linkage The new methodology can be found in the re-worded comment, but the gist of it is that -C prefer-dynamic doesn't turn off static linkage. The error messages should also be a little more sane now. Closes #12133 2014-02-10 13:33:33 -06:00			`//@ aux-build:issue-12133-rlib.rs`
			`//@ aux-build:issue-12133-dylib.rs`
rustc: Add some suppot for mixing rlibs and dylibs Currently, rustc requires that a linkage be a product of 100% rlibs or 100% dylibs. This is to satisfy the requirement that each object appear at most once in the final output products. This is a bit limiting, and the upcoming libcore library cannot exist as a dylib, so these rules must change. The goal of this commit is to enable some use cases for mixing rlibs and dylibs, primarily libcore's use case. It is not targeted at allowing an exhaustive number of linkage flavors. There is a new dependency_format module in rustc which calculates what format each upstream library should be linked as in each output type of the current unit of compilation. The module itself contains many gory details about what's going on here. cc #10729 2014-05-02 02:59:27 -05:00			`//@ aux-build:issue-12133-dylib2.rs`
Update test directives for `wasm32-wasip1` * The WASI targets deal with the `main` symbol a bit differently than native so some `codegen` and `assembly` tests have been ignored. * All `ignore-emscripten` directives have been updated to `ignore-wasm32` to be more clear that all wasm targets are ignored and it's not just Emscripten. * Most `ignore-wasm32-bare` directives are now gone. * Some ignore directives for wasm were switched to `needs-unwind` instead. * Many `ignore-wasm32*` directives are removed as the tests work with WASI as opposed to `wasm32-unknown-unknown`. 2024-03-06 14:44:54 -06:00			`//@ ignore-wasm32 no dylib support`
Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI. It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically. 2018-01-02 07:11:41 -06:00			`//@ ignore-musl`
add support for needs-dynamic-linking 2023-05-17 03:41:41 -05:00			`//@ needs-dynamic-linking`
Tweak how preference factors into linkage The new methodology can be found in the re-worded comment, but the gist of it is that -C prefer-dynamic doesn't turn off static linkage. The error messages should also be a little more sane now. Closes #12133 2014-02-10 13:33:33 -06:00
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00			`//@ pretty-expanded FIXME #23616`

Fix fallout of removing quotes in crate names 2015-03-27 12:22:44 -05:00			`extern crate issue_12133_dylib2 as other;`
Tweak how preference factors into linkage The new methodology can be found in the re-worded comment, but the gist of it is that -C prefer-dynamic doesn't turn off static linkage. The error messages should also be a little more sane now. Closes #12133 2014-02-10 13:33:33 -06:00
			`fn main() {}`