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

// run-pass
// aux-build:foreign_lib.rs
// ignore-wasm32-bare no libc to test ffi with

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

// pretty-expanded FIXME #23616

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 16:54:25 -05: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 18:18:37 -05:00			`// aux-build:foreign_lib.rs`
std: Add a new wasm32-unknown-unknown target This commit adds a new target to the compiler: wasm32-unknown-unknown. This target is a reimagining of what it looks like to generate WebAssembly code from Rust. Instead of using Emscripten which can bring with it a weighty runtime this instead is a target which uses only the LLVM backend for WebAssembly and a "custom linker" for now which will hopefully one day be direct calls to lld. Notable features of this target include: * There is zero runtime footprint. The target assumes nothing exists other than the wasm32 instruction set. * There is zero toolchain footprint beyond adding the target. No custom linker is needed, rustc contains everything. * Very small wasm modules can be generated directly from Rust code using this target. * Most of the standard library is stubbed out to return an error, but anything related to allocation works (aka `HashMap`, `Vec`, etc). * Naturally, any `#[no_std]` crate should be 100% compatible with this new target. This target is currently somewhat janky due to how linking works. The "linking" is currently unconditional whole program LTO (aka LLVM is being used as a linker). Naturally that means compiling programs is pretty slow! Eventually though this target should have a linker. This target is also intended to be quite experimental. I'm hoping that this can act as a catalyst for further experimentation in Rust with WebAssembly. Breaking changes are very likely to land to this target, so it's not recommended to rely on it in any critical capacity yet. We'll let you know when it's "production ready". --- Currently testing-wise this target is looking pretty good but isn't complete. I've got almost the entire `run-pass` test suite working with this target (lots of tests ignored, but many passing as well). The `core` test suite is still getting LLVM bugs fixed to get that working and will take some time. Relatively simple programs all seem to work though! --- It's worth nothing that you may not immediately see the "smallest possible wasm module" for the input you feed to rustc. For various reasons it's very difficult to get rid of the final "bloat" in vanilla rustc (again, a real linker should fix all this). For now what you'll have to do is: cargo install --git https://github.com/alexcrichton/wasm-gc wasm-gc foo.wasm bar.wasm And then `bar.wasm` should be the smallest we can get it! --- In any case for now I'd love feedback on this, particularly on the various integration points if you've got better ideas of how to approach them! 2017-10-22 22:01:00 -05:00			`// ignore-wasm32-bare no libc to test ffi with`
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 14:14:01 -05:00
			`// The purpose of this test is to check that we can`
Add "cdecl" as synonym for "c-stack-cdecl" 2011-11-09 18:04:07 -06: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 14:14:01 -05: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 15:13:15 -05: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 12:10:06 -06:00			`extern crate foreign_lib;`
core: Clean up comments and exports 2012-03-10 02:04:09 -06:00
check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
librustc: Stop reexporting the standard modules from prelude. 2013-05-24 21:35:29 -05:00			`unsafe {`
Fix warnings it tests 2013-08-17 10:37:42 -05:00			`let _foo = foreign_lib::rustrt::rust_get_test_int();`
librustc: Stop reexporting the standard modules from prelude. 2013-05-24 21:35:29 -05:00			`}`
re-enable tests for #1058 and #1059 2011-11-18 18:29:01 -06:00			`}`