Future-proof pp_trans against a possible future undefined behaviour

If do_trans() ever wants to modify the stack in the future, this would
cause an undefined behaviour as mPUSHi() invokes its parameter on the same
argument list as PUSHmortal, which itself touches the stack.

1 files changed, 2 insertions, 1 deletions

diff --git a/pp.c b/pp.c
index 05268f4c35..6a844c26e0 100644
--- a/pp.c
+++ b/pp.c
@@ -762,7 +762,8 @@ PP(pp_trans)
 	PUSHs(newsv);
     }
     else {
-	mPUSHi(do_trans(sv));
+	I32 i = do_trans(sv);
+	mPUSHi(i);
     }
     RETURN;
 }