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

// run-pass
// revisions: x64 x32
// [x64]only-x86_64
// [x32]only-x86

#![feature(abi_vectorcall)]

trait A {
    extern "vectorcall" fn test1(i: i32);
}

struct S;

impl A for S {
    extern "vectorcall" fn test1(i: i32) {
        assert_eq!(i, 1);
    }
}

extern "vectorcall" fn test2(i: i32) {
    assert_eq!(i, 2);
}

fn main() {
    <S as A>::test1(1);
    test2(2);
}
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`
Replace per-target ABI denylist with an allowlist It makes very little sense to maintain denylists of ABIs when, as far as non-generic ABIs are concerned, targets usually only support a small subset of the available ABIs. This has historically been a cause of bugs such as us allowing use of the platform-specific ABIs on x86 targets – these in turn would cause LLVM errors or assertions to fire. Fixes #57182 Sponsored by: standard.ai 2021-06-11 14:22:13 +03:00			`// revisions: x64 x32`
			`// [x64]only-x86_64`
Fix tests using `only-i686` to use the correct `only-x86` directive We translate `i686` to `x86` which means tests marked as `only-i686` never ran. Update those tests to use `only-x86`. 2021-11-04 10:30:23 -04:00			`// [x32]only-x86`
adapt tests 2016-10-25 19:56:36 +02:00
test: add a basic test for the vectorcall calling convention 2016-01-12 21:21:28 +01:00			`#![feature(abi_vectorcall)]`

			`trait A {`
			`extern "vectorcall" fn test1(i: i32);`
			`}`

			`struct S;`

			`impl A for S {`
			`extern "vectorcall" fn test1(i: i32) {`
			`assert_eq!(i, 1);`
			`}`
			`}`

			`extern "vectorcall" fn test2(i: i32) {`
			`assert_eq!(i, 2);`
			`}`

			`fn main() {`
			`<S as A>::test1(1);`
			`test2(2);`
			`}`