| commit | e43f970c7ff6aa7e410a59b275542db678c7f2d7 | |
| author | Hans-Peter Nilsson <hp@axis.com> | |
| Fri, 3 Mar 2023 20:23:06 +0000 (3 21:23 +0100) | ||
| committer | Hans-Peter Nilsson <hp@bitrange.com> | |
| Tue, 7 Mar 2023 01:23:57 +0000 (7 02:23 +0100) | ||
| tree | 1f0cd97ca4e3071f6bff54b6ec02a397169f2ec1 | treesnapshot (tar.gz zip) |
| parent | 318c9101a3bc24e4cd1a89eeb52531988a11c89f | commitdiff |
testsuite: Gate gcc.dg/plugin/must-tail-call-1.c and -2.c on tail_call
While gcc.dg/plugin/must-tail-call-2.c passes for all targets even
without this, the error message is, for a target like cris-elf that
doesn't implement sibling calls: "error: cannot tail-call: machine
description does not have a sibcall_epilogue instruction pattern"
rather than "error: cannot tail-call: callee returns a structure".
Also, it'd be confusing to exclude must-tail-call-1.c but not
must-tail-call-2.c
* gcc.dg/plugin/must-tail-call-1.c, gcc.dg/plugin/must-tail-call-2.c:
Gate on effective target tail_call.
While gcc.dg/plugin/must-tail-call-2.c passes for all targets even
without this, the error message is, for a target like cris-elf that
doesn't implement sibling calls: "error: cannot tail-call: machine
description does not have a sibcall_epilogue instruction pattern"
rather than "error: cannot tail-call: callee returns a structure".
Also, it'd be confusing to exclude must-tail-call-1.c but not
must-tail-call-2.c
* gcc.dg/plugin/must-tail-call-1.c, gcc.dg/plugin/must-tail-call-2.c:
Gate on effective target tail_call.
| gcc/testsuite/gcc.dg/plugin/must-tail-call-1.c | diffblobblamehistory | |
| gcc/testsuite/gcc.dg/plugin/must-tail-call-2.c | diffblobblamehistory |