rust/tests/ui/linkage-attr/linkage-import.rs

//@ build-pass
//@ aux-build:def_external.rs

extern crate def_external as dep;

fn main() {
    println!("{:p}", &dep::EXTERN);
}
Move linkage type check to HIR analysis and fix semantics issues. This ensures that the error is printed even for unused variables, as well as unifying the handling between the LLVM and GCC backends. This also fixes unusual behavior around exported Rust-defined variables with linkage attributes. With the previous behavior, it appears to be impossible to define such a variable such that it can actually be imported and used by another crate. This is because on the importing side, the variable is required to be a pointer, but on the exporting side, the type checker rejects static variables of pointer type because they do not implement `Sync`. Even if it were possible to import such a type, it appears that code generation on the importing side would add an unexpected additional level of pointer indirection, which would break type safety. This highlighted that the semantics of linkage on Rust-defined variables is different to linkage on foreign items. As such, we now model the difference with two different codegen attributes: linkage for Rust-defined variables, and import_linkage for foreign items. This change gives semantics to the test src/test/ui/linkage-attr/auxiliary/def_illtyped_external.rs which was previously expected to fail to compile. Therefore, convert it into a test that is expected to successfully compile. The update to the GCC backend is speculative and untested. 2022-11-23 20:13:30 -06:00			`//@ build-pass`
			`//@ aux-build:def_external.rs`

			`extern crate def_external as dep;`

			`fn main() {`
			`println!("{:p}", &dep::EXTERN);`
			`}`