authorgravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2025-12-11 19:26:41+01:00
committergravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2025-12-16 06:22:51+01:00
logeaae3f936bf047186453fa2ec1d99ba684edede8
tree8404a19e7453cfba585273086232ade376173068
parentf36949ead358e2fa4430454e15685e60e6bd07f5
signaturebadge-check Signed by SSH key SHA256:7B/LJ7bpR1eX8aCXSr4mtd5M45VMPKcx9zY8e95b5QM

test: limit `invalid_tail_call` to x86_64-linux

Targets that don't support tail calls will see: /home/ci/zig/.zig-cache/o/35dbe82c8e4d49ae5b7d630329568133/tmp.zig:5:5: error: unable to perform tail call: compiler backend 'stage2_llvm' does not support tail calls on target architecture 'powerpc64le' with the selected CPU feature flags So just run this test on a known-good target.

1 files changed, 1 insertions(+), 0 deletions(-)

test/cases/compile_errors/invalid_tail_call.zig+1
......@@ -7,5 +7,6 @@ pub export fn entry() void {
77
88// error
99// backend=llvm
10// target=x86_64-linux
1011//
1112// :5:5: error: unable to perform tail call: type of function being called 'fn (usize) void' does not match type of calling function 'fn () callconv(.c) void'