rust/src/test/ui/parser/issue-8537.stderr

error[E0703]: invalid ABI: found `invalid-ab_isize`
  --> $DIR/issue-8537.rs:2:3
   |
LL |   "invalid-ab_isize"
   |   ^^^^^^^^^^^^^^^^^^ invalid ABI
   |
   = help: valid ABIs: cdecl, stdcall, fastcall, vectorcall, thiscall, aapcs, win64, sysv64, ptx-kernel, msp430-interrupt, x86-interrupt, amdgpu-kernel, efiapi, Rust, C, system, rust-intrinsic, rust-call, platform-intrinsic, unadjusted

error: aborting due to previous error
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			error[E0703]: invalid ABI: found `invalid-ab_isize`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`--> $DIR/issue-8537.rs:2:3`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| "invalid-ab_isize"`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\| ^^^^^^^^^^^^^^^^^^ invalid ABI`
			`\|`
Add new EFIAPI ABI Adds a new ABI for the EFIAPI calls. This ABI should reflect the latest version of the UEFI specification at the time of commit (UEFI spec 2.8, URL below). The specification says that for x86_64, we should follow the win64 ABI, while on all other supported platforms (ia32, itanium, arm, arm64 and risc-v), we should follow the C ABI. To simplify the implementation, we will simply follow the C ABI on all platforms except x86_64, even those technically unsupported by the UEFI specification. https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf 2019-10-24 10:29:29 -05:00			`= help: valid ABIs: cdecl, stdcall, fastcall, vectorcall, thiscall, aapcs, win64, sysv64, ptx-kernel, msp430-interrupt, x86-interrupt, amdgpu-kernel, efiapi, Rust, C, system, rust-intrinsic, rust-call, platform-intrinsic, unadjusted`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
			`error: aborting due to previous error`