void functions don't need to indicate lack of return

The somewhat confusingly named NORETURN_FUNCTION_END, introduced
in 0dbb1585a715e563, apparently indicates that the function
expects a return but isn't getting one.  Since void functions
don't expect a return, it isn't appropriate for them, and in fact,
since the macro includes a return statement, some compilers will
whinge about returning from a void function.

1 files changed, 0 insertions, 2 deletions

diff --git a/toke.c b/toke.c
index a63b69a7b0..bc1caba259 100644
--- a/toke.c
+++ b/toke.c
@@ -6635,8 +6635,6 @@ yyl_croak_unrecognised(pTHX_ char *s)
     Perl_croak(aTHX_  "Unrecognized character %s; marked by <-- HERE after %" UTF8f "<-- HERE near column %d", c,
                       UTF8fARG(UTF, (s - d), d),
                      (int) len + 1);
-
-    NORETURN_FUNCTION_END;
 }
 
 static int