From b0af9ac7331e3efa0dcee4f43b2ba8b1e4e52f2f Mon Sep 17 00:00:00 2001 From: Nikita Popov Date: Fri, 16 Feb 2018 21:25:49 +0100 Subject: Avoid live range references in opcodes Don't store the live range of the freed variable for FREE_ON_RETURN frees, instead look it up at runtime. As this is an extremely unlikely codepath (in particular, it requires a loop variable with a throwing destructor), saving the runtime lookup of the live range is not worth the extra complexity this adds everywhere else. --- Zend/zend_vm_opcodes.h | 1 - 1 file changed, 1 deletion(-) (limited to 'Zend/zend_vm_opcodes.h') diff --git a/Zend/zend_vm_opcodes.h b/Zend/zend_vm_opcodes.h index 6f9b323bb0..b5c0a483d8 100644 --- a/Zend/zend_vm_opcodes.h +++ b/Zend/zend_vm_opcodes.h @@ -42,7 +42,6 @@ #define ZEND_VM_OP_NUM 0x00000010 #define ZEND_VM_OP_JMP_ADDR 0x00000020 #define ZEND_VM_OP_TRY_CATCH 0x00000030 -#define ZEND_VM_OP_LIVE_RANGE 0x00000040 #define ZEND_VM_OP_THIS 0x00000050 #define ZEND_VM_OP_NEXT 0x00000060 #define ZEND_VM_OP_CLASS_FETCH 0x00000070 -- cgit v1.2.1