rust/tests/ui/cross-crate/xcrate-static-addresses.rs

// run-pass
// aux-build:xcrate_static_addresses.rs

// pretty-expanded FIXME #23616

extern crate xcrate_static_addresses;

use xcrate_static_addresses as other;

pub fn main() {
    other::verify_same(&other::global);
    other::verify_same2(other::global2);
}
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 14:18:55 +02:00			`// run-pass`
Resolve globals having different addresses across crates * All globals marked as `pub` won't have the `internal` linkage type set * All global references across crates are forced to use the address of the global in the other crate via an external reference. 2013-08-01 01:53:41 -07:00			`// aux-build:xcrate_static_addresses.rs`

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 13:13:15 -07:00			`// pretty-expanded FIXME #23616`

extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 10:10:06 -08:00			`extern crate xcrate_static_addresses;`
Resolve globals having different addresses across crates * All globals marked as `pub` won't have the `internal` linkage type set * All global references across crates are forced to use the address of the global in the other crate via an external reference. 2013-08-01 01:53:41 -07:00
libsyntax: Accept `use foo as bar;` in lieu of `use bar as foo;` The old syntax will be removed after a snapshot. RFC #47. Issue #16461. 2014-08-12 19:25:05 -07:00			`use xcrate_static_addresses as other;`
Resolve globals having different addresses across crates * All globals marked as `pub` won't have the `internal` linkage type set * All global references across crates are forced to use the address of the global in the other crate via an external reference. 2013-08-01 01:53:41 -07:00
			`pub fn main() {`
			`other::verify_same(&other::global);`
Resume inlining globals across crates In #8185 cross-crate condition handlers were fixed by ensuring that globals didn't start appearing in different crates with different addressed. An unfortunate side effect of that pull request is that constants weren't inlined across crates (uint::bits is unknown to everything but libstd). This commit fixes this inlining by using the `available_eternally` linkage provided by LLVM. It partially reverts #8185, and then adds support for this linkage type. The main caveat is that not all statics could be inlined into other crates. Before this patch, all statics were considered "inlineable items", but an unfortunate side effect of how we deal with `&static` and `&[static]` means that these two cases cannot be inlined across crates. The translation of constants was modified to propogate this condition of whether a constant should be considered inlineable into other crates. Closes #9036 2013-09-11 10:06:16 -07:00			`other::verify_same2(other::global2);`
Resolve globals having different addresses across crates * All globals marked as `pub` won't have the `internal` linkage type set * All global references across crates are forced to use the address of the global in the other crate via an external reference. 2013-08-01 01:53:41 -07:00			`}`