Voidify zend_ssa_compute_use_def_chains()

It always returned SUCCESS

Voidify zend_ssa_find_false_dependencies()

It always returned SUCCESS

Voidify zend_ssa_find_sccs()

It always returned SUCCESS

Voidify zend_cfg_identify_loops()

It always returned SUCCESS

Voidify zend_cfg_compute_dominators_tree()

It always returned SUCCESS

Voidify zend_cfg_build_predecessors()

It always returned SUCCESS

Voidify zend_build_cfg()

It always returned SUCCESS

Voidify zend_analyze_calls()

It always returned SUCCESS

Voidify zend_build_call_graph()

It always returned SUCCESS

JIT: Move unusual checks for IS_REFERENCE to cold paths.

Don't jit FE_RESET_R with undef operand

The implementation currently assumes that the operand is always
an array, but this did not account for a possibly undef operand.

Tracing JIT: Record information about elements of arrays and use it to improve generated code (ASSIGN_DIM).

Display DASM_S_UNDEF_PC argument

Fix JIT call chain check without call opcode

The do_fcall opcode may have been optimized away if an opcode like
exit is present in the arguments. In that case the opcode scan
would g

Fix JIT call chain check without call opcode

The do_fcall opcode may have been optimized away if an opcode like
exit is present in the arguments. In that case the opcode scan
would go past the end of the op array.

show more ...

Also make sure binary op operands can't be undef

Otherwise we will end up passing undef to xyz_function etc, which
is not permitted.

Check whether expected types are present for compound op jit

zend_jit_long_math_helper() implicitly assumes that the operands
MAY_BE_LONG (but can also have additional types). It will no

Check whether expected types are present for compound op jit

zend_jit_long_math_helper() implicitly assumes that the operands
MAY_BE_LONG (but can also have additional types). It will normally
only be called if this is guaranteed. However, for compound
array/object assignment ops this was not check. Generalize the
existing check for assign_op to apply to these as well.

Of course, we could also make the code support this correctly,
but I don't think it makes sense to JIT these if the type we're
specializing for is not present.

Closes GH-7481.

show more ...

JIT: improved code for protected properties access

JIT: eliminate check for undefined constant if there is a persistent constant

Fixed bug #81409 (Incorrect JIT code for ADD with a reference to array)

JIT: Allow keeping result of FETCH_CONSTANT in a CPU register

JIT: Optimize zend_vm_stack_free_args()

Avoid code genearation for destructors of immutable parameters of internal functions that cannot be changed in place.
Keep destructors for immutab

JIT: Optimize zend_vm_stack_free_args()

Avoid code genearation for destructors of immutable parameters of internal functions that cannot be changed in place.
Keep destructors for immutable array parameters, because few function may modufy them in-pace.

show more ...

Avoid redundand repeatable VM stack overflow checks

JIT: Code generation for ROPE_INIT, ROPE_ADD and ROPE_END with STRING operands

Fixed bug #81226 (Integer overflow behavior is different with JIT enabled)

Fix #81206: Multiple PHP processes crash with JIT enabled

We need to avoid resetting the JIT for all SAPIs, but we need to
initialize the JIT handlers even when only reattaching on Windo

Fix #81206: Multiple PHP processes crash with JIT enabled

We need to avoid resetting the JIT for all SAPIs, but we need to
initialize the JIT handlers even when only reattaching on Windows.

Closes GH-7208.

show more ...