From ea2ae026078b328ddeab060940568a4d3bf1b417 Mon Sep 17 00:00:00 2001
From: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
Date: Fri, 15 Apr 2022 20:19:24 +0100
Subject: gh-91276: Make JUMP_IF_TRUE_OR_POP/JUMP_IF_FALSE_OR_POP relative
 (GH-32215)

---
 Python/compile.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'Python/compile.c')

diff --git a/Python/compile.c b/Python/compile.c
index 718b521858b..3b91566efba 100644
--- a/Python/compile.c
+++ b/Python/compile.c
@@ -7672,6 +7672,21 @@ normalize_jumps(struct assembler *a)
                     last->i_opcode = is_forward ?
                         POP_JUMP_FORWARD_IF_TRUE : POP_JUMP_BACKWARD_IF_TRUE;
                     break;
+                case JUMP_IF_TRUE_OR_POP:
+                case JUMP_IF_FALSE_OR_POP:
+                    if (!is_forward) {
+                        /* As far as we can tell, the compiler never emits
+                         * these jumps with a backwards target. If/when this
+                         * exception is raised, we have found a use case for
+                         * a backwards version of this jump (or to replace
+                         * it with the sequence (COPY 1, POP_JUMP_IF_T/F, POP)
+                         */
+                        PyErr_Format(PyExc_SystemError,
+                            "unexpected %s jumping backwards",
+                            last->i_opcode == JUMP_IF_TRUE_OR_POP ?
+                                "JUMP_IF_TRUE_OR_POP" : "JUMP_IF_FALSE_OR_POP");
+                    }
+                    break;
             }
         }
     }
-- 
cgit v1.2.3