rust/tests/incremental/issue-54059.rs

//@ aux-build:issue-54059.rs
//@ ignore-wasm32-bare no libc for ffi testing
//@ ignore-windows - dealing with weird symbols issues on dylibs isn't worth it
//@ revisions: rpass1

extern crate issue_54059;

fn main() {}
Moved issue tests to subdirs and normalised names. 2019-03-11 19:49:17 -05:00			`//@ aux-build:issue-54059.rs`
avoid leaking host details in proc macro metadata decoding proc macro crates are essentially implemented as dynamic libraries using a dlopen-based ABI. They are also Rust crates, so they have 2 worlds - the "host" world in which they are defined, and the "target" world in which they are used. For all the "target" world knows, the proc macro crate might not even be implemented in Rust, so leaks of details from the host to the target must be avoided for correctness. Because the "host" DefId space is different from the "target" DefId space, any leak involving a DefId will have a nonsensical or out-of-bounds DefKey, and will cause all sorts of crashes. This PR fixes all leaks I have found in `decoder`. In particular, #54059 was caused by host native libraries leaking into the target, which feels like it might even be a correctness issue if it doesn't cause an ICE. Fixes #54059 2018-09-15 15:26:04 -05:00			`//@ ignore-wasm32-bare no libc for ffi testing`
Ignore new test on Windows 2018-09-21 12:05:23 -05:00			`//@ ignore-windows - dealing with weird symbols issues on dylibs isn't worth it`
avoid leaking host details in proc macro metadata decoding proc macro crates are essentially implemented as dynamic libraries using a dlopen-based ABI. They are also Rust crates, so they have 2 worlds - the "host" world in which they are defined, and the "target" world in which they are used. For all the "target" world knows, the proc macro crate might not even be implemented in Rust, so leaks of details from the host to the target must be avoided for correctness. Because the "host" DefId space is different from the "target" DefId space, any leak involving a DefId will have a nonsensical or out-of-bounds DefKey, and will cause all sorts of crashes. This PR fixes all leaks I have found in `decoder`. In particular, #54059 was caused by host native libraries leaking into the target, which feels like it might even be a correctness issue if it doesn't cause an ICE. Fixes #54059 2018-09-15 15:26:04 -05:00			`//@ revisions: rpass1`

			`extern crate issue_54059;`

			`fn main() {}`