rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
51b51b51d7931da85280382a81c4dd80c73ca754
rust/tests/ui/feature-gates/feature-gate-vectorcall.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

74 lines
3.3 KiB
Plaintext
Raw Normal View History

tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:14:8
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
|
LL | extern "vectorcall" fn f() {}
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:17:12
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
|
LL | extern "vectorcall" fn m();
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:19:12
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
|
LL | extern "vectorcall" fn dm() {}
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:24:12
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
|
LL | extern "vectorcall" fn m() {}
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:28:12
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
|
LL | extern "vectorcall" fn im() {}
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:31:18
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
|
LL | type TA = extern "vectorcall" fn();
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
tests: error strings for ABI stability now match
2025-02-05 11:15:27 -08:00
error[E0658]: the extern "vectorcall" ABI is experimental and subject to change
tests: use minicore more minicore makes it much easier to add new language items to all of the existing `no_core` tests.
2025-02-24 09:26:54 +00:00
--> $DIR/feature-gate-vectorcall.rs:33:8
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
|
LL | extern "vectorcall" {}
| ^^^^^^^^^^^^
|
Add tracking issue and unstable book page for `"vectorcall"` ABI
2024-04-28 19:22:51 +01:00
= note: see issue #124485 <https://github.com/rust-lang/rust/issues/124485> for more information
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
= help: add `#![feature(abi_vectorcall)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 01:39:02 -05:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
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
error: aborting due to 7 previous errors
For more information about this error, try `rustc --explain E0658`.
Reference in New Issue Copy Permalink