rust/tests/ui/extern/extern-rust.rs

//@ run-pass

#[repr(C)]
pub struct Foo(u32);

// ICE trigger, bad handling of differing types between rust and external ABIs
pub extern "C" fn bar() -> Foo {
    Foo(0)
}

fn main() {}
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`
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
Fix ICE when compiling "extern" rust functions As the function comment already says, the types generated in the foreign_signture function don't necessarily match the types used for a corresponding rust function. Therefore we can't just use these types to guide the translation of the wrapper function that bridges between the external ABI and the rust ABI. Instead, we can query LLVM about the types used in the rust function and use those to generate an appropriate wrapper. Fixes #21454 2015-02-10 23:43:38 +01:00			`#[repr(C)]`
			`pub struct Foo(u32);`

			`// ICE trigger, bad handling of differing types between rust and external ABIs`
Update code to account for extern ABI requirement 2020-09-01 17:28:11 -04:00			`pub extern "C" fn bar() -> Foo {`
Fix ICE when compiling "extern" rust functions As the function comment already says, the types generated in the foreign_signture function don't necessarily match the types used for a corresponding rust function. Therefore we can't just use these types to guide the translation of the wrapper function that bridges between the external ABI and the rust ABI. Instead, we can query LLVM about the types used in the rust function and use those to generate an appropriate wrapper. Fixes #21454 2015-02-10 23:43:38 +01:00			`Foo(0)`
			`}`

			`fn main() {}`