I added this test back in r7-934-g15c671a79ca66d, but it looks like
r15-2125-g81824596361cf4 changed the error message.
Tested on x86_64-pc-linux-gnu.
Pushed to trunk as r16-3172-gf622df9af2e7c1.
gcc/testsuite/ChangeLog:
PR testsuite/119783
jit.dg/test-error-impossible-must-tail-call.c
* jit.dg/test-error-impossible-must-tail-call.c (verify_code):
Check that we get a suitable-looking error message, but don't
try to specify exactly what the message is.
---
gcc/testsuite/jit.dg/test-error-impossible-must-tail-call.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/jit.dg/test-error-impossible-must-tail-call.c
b/gcc/testsuite/jit.dg/test-error-impossible-must-tail-call.c
index 8848d3015a9a..a50dcb2f43c1 100644
--- a/gcc/testsuite/jit.dg/test-error-impossible-must-tail-call.c
+++ b/gcc/testsuite/jit.dg/test-error-impossible-must-tail-call.c
@@ -88,6 +88,8 @@ verify_code (gcc_jit_context *ctxt, gcc_jit_result *result)
{
CHECK_VALUE (result, NULL);
- CHECK_STRING_VALUE (gcc_jit_context_get_first_error (ctxt),
- "cannot tail-call: callee returns a structure");
+ /* Check that we get an error message with a reason; we
+ don't want to overspecify the test with a precise reason, though. */
+ CHECK_STRING_STARTS_WITH (gcc_jit_context_get_first_error (ctxt),
+ "cannot tail-call: ");
}
--
2.26.3
