add PMf_CODELIST_PRIVATE flag

This indicates that the op_code_list field in a PMOP is "private";
that is, it points to a list of DO blocks that we don't own, and
shouldn't free, and whose pad may not match ours.

This will allow us to use the op_code_list field in the runtime case of
literal code, e.g. /$runtime(?{...})/ and qr/$runtime(?{...})/. Here, at
compile-time, we need to make the pre-compiled (?{..}) blocks available to
pp_regcomp, but the list containing those blocks is also the list that is
executed in the lead-up to executing pp_regcomp (while skipping the DO
blocks), so the code is already embedded, and doesn't need freeing.
Furthermore, in the qr// case, the code blocks are actually within a
different sub (an anon one) than the PMOP, so the pads won't match.

1 files changed, 5 insertions, 1 deletions

diff --git a/op.h b/op.h
index 4f5710bdfb..06437d475f 100644
--- a/op.h
+++ b/op.h
@@ -437,7 +437,11 @@ struct pmop {
 /* the pattern has a CV attached (currently only under qr/...(?{}).../) */
 #define PMf_HAS_CV	(1<<(PMf_BASE_SHIFT+10))
 
-#if PMf_BASE_SHIFT+10 > 31
+/* op_code_list is private; don't free it etc. It may well point to
+ * code within another sub, with different pad etc */
+#define PMf_CODELIST_PRIVATE	(1<<(PMf_BASE_SHIFT+11))
+
+#if PMf_BASE_SHIFT+11 > 31
 #   error Too many PMf_ bits used.  See above and regnodes.h for any spare in middle
 #endif