[perl #118693] Remove PADTMP exemption from uninit warnings

This fixes a problem with undefined values return from XSUBs not pro-
ducing such warnings.

The default typemap for XSUBs uses the target of the entersub call (in
the caller’s pad) to return the converted value, instead of having to
allocate a new SV for that.

So, for example, a function returning char* will cause that char* to
be assigned to the target via sv_setpv.  Then the target is returned.

As a special case, NULL return from a char*-returning function will
produce an undef return value.  This undef return value was not trig-
gering an uninitialized warning.

All targets are marked PADTMP, and anything marked PADTMP is exempt
from uninitialized warnings in some code paths, but not others.

This goes all the way back to 91bba347, which suppressed the warning
with only a hit at why (something to do with bitwise ops warning inap-
propriately).  I think it was to make ~undef exempt.  But a1afd104
stopped it from being exempt.

Only a few pieces of code were relying on this exemption, and it was
hiding bugs, too.  The last few commits have addressed those, so kiss
this exemption good-bye!

pp_reverse had a workaround to force an uninit warning (since
1e21d011c), so remove the workaround to avoid a double uninit warning.

1 files changed, 0 insertions, 2 deletions

diff --git a/pp.c b/pp.c
index 8e5ba2be22..fd40453657 100644
--- a/pp.c
+++ b/pp.c
@@ -5267,8 +5267,6 @@ PP(pp_reverse)
 	    do_join(TARG, &PL_sv_no, MARK, SP);
 	else {
 	    sv_setsv(TARG, SP > MARK ? *SP : find_rundefsv());
-	    if (! SvOK(TARG) && ckWARN(WARN_UNINITIALIZED))
-		report_uninit(TARG);
 	}
 
 	up = SvPV_force(TARG, len);