rust/tests/ui/abi/foreign/invoke-external-foreign.rs

//@ run-pass
//@ aux-build:foreign_lib.rs

// The purpose of this test is to check that we can
// successfully (and safely) invoke external, cdecl
// functions from outside the crate.


extern crate foreign_lib;

pub fn main() {
    unsafe {
        let _foo = foreign_lib::rustrt::rust_get_test_int();
    }
}
tests: Add missing run-pass annotations 2019-07-26 21:54:25 +00:00			`//@ run-pass`
Change 'native' and 'crust' to 'extern'. This comes with a terminology change. All linkage-symbols are 'extern' now, including rust syms in other crates. Some extern ABIs are merely "foreign". The term "native" is retired, not clear/useful. What was "crust" is now "extern" applied to a _definition_. This is a bit of an overloading, but should be unambiguous: it means that the definition should be made available to some non-rust ABI. 2012-06-26 23:18:37 +00:00			`//@ aux-build:foreign_lib.rs`
work around bug when calling c-stack-cdecl fns from outside crate In the main test, I call the wrapper instead of the native fn, as intended. I also added an xfail-test that exercises the broken code path. Will file a bug. Description of the broken code path: The code path is that when we look up the external identifier we go through trans_external_path() -> type_of_ty_param_kinds_and_ty() -> type_of_fn_from_ty() -> type_of_fn(), and type_of_fn() adds a lot of external parameters. Problem is, I guess, that we don't pass the native ABI (or even the fact that it's a native function!), just the types and kinds of the parameters. 2011-10-21 19:14:01 +00:00
			`// The purpose of this test is to check that we can`
Add "cdecl" as synonym for "c-stack-cdecl" 2011-11-10 00:04:07 +00:00			`// successfully (and safely) invoke external, cdecl`
work around bug when calling c-stack-cdecl fns from outside crate In the main test, I call the wrapper instead of the native fn, as intended. I also added an xfail-test that exercises the broken code path. Will file a bug. Description of the broken code path: The code path is that when we look up the external identifier we go through trans_external_path() -> type_of_ty_param_kinds_and_ty() -> type_of_fn_from_ty() -> type_of_fn(), and type_of_fn() adds a lot of external parameters. Problem is, I guess, that we don't pass the native ABI (or even the fact that it's a native function!), just the types and kinds of the parameters. 2011-10-21 19:14:01 +00:00			`// functions from outside the crate.`

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 20:13:15 +00:00
extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 18:10:06 +00:00			`extern crate foreign_lib;`
core: Clean up comments and exports 2012-03-10 08:04:09 +00:00
check-fast fallout from removing export, r=burningtree 2013-02-02 03:43:17 +00:00			`pub fn main() {`
librustc: Stop reexporting the standard modules from prelude. 2013-05-25 02:35:29 +00:00			`unsafe {`
Fix warnings it tests 2013-08-17 15:37:42 +00:00			`let _foo = foreign_lib::rustrt::rust_get_test_int();`
librustc: Stop reexporting the standard modules from prelude. 2013-05-25 02:35:29 +00:00			`}`
re-enable tests for #1058 and #1059 2011-11-19 00:29:01 +00:00			`}`