Discard disasm symbols on opcache restart

Fix incorrect condition introdused in 7cf6f173831caea9952a84b9e4a93594aac8ba00

Fixed bug GH-8847 (PHP hanging infinitly at 100% cpu when check php syntaxe of a valid file)

JIT: Fix register allocation

Fixes oss-fuzz #44689

JIT: Fix missed type store

Fizes oss-fuzz #44376

Fix incorrect register allocation

Fixes oss-fuzz #44006

Fix #81679: Tracing JIT crashes on reattaching

When a new process reattaches to OPcache, tracing JIT causes segfaults,
because each new process allocates its own `zend_jit_traces` and

Fix #81679: Tracing JIT crashes on reattaching

When a new process reattaches to OPcache, tracing JIT causes segfaults,
because each new process allocates its own `zend_jit_traces` and
`zend_jit_exit_groups` in SHM, although these need to be shared between
all processes.

We solve that by only allocating these structs for the first process,
and store the pointers in `accel_shared_globals`, so we can reassign
them when a new process reattaches.

Closes GH-7776.

show more ...

JIT: Fix crash during compilation of function with incompletely constructed SSA

Fixes oss-fuzz #42200

JIT: Fix incorrect elimination of type store

Fixes oss-fuzz #41995

JIT: Fix named arguments handling

Fixes oss-fuzz #41486

Disable type narrowing optimization when we contruct SSA for JIT

This also revets incorrect fix introduced in f9518c3850982aca41fac22b87a1e11096eb1643

Check for zend_shared_alloc() failures

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.

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 ...

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 ...

Disable ASSIGN + SEND_VAL fusion for cases when destroying of old value may throw an exception.

Fixed JIT on first function execution (opcache.jit=1215) with CALL VM

Backport "ignore some opcodes in the JIT check"

This is a backport of fc64a7bef4c53f1948ced1043debd2024fd20f6f to the PHP-8.0 branch so that extensions don’t have to bypass the JIT check in

Backport "ignore some opcodes in the JIT check"

This is a backport of fc64a7bef4c53f1948ced1043debd2024fd20f6f to the PHP-8.0 branch so that extensions don’t have to bypass the JIT check in a hacky way.

show more ...

Fixed bug #80745 (JIT produces Assert failure and UNKNOWN:0 var_dumps in code involving bitshifts)

Keep JIT region executable under ZTS

When one thread tries to compile a script, another thread may
already be executing JITed code. In this case we can't make the
memory non-executab

Keep JIT region executable under ZTS

When one thread tries to compile a script, another thread may
already be executing JITed code. In this case we can't make the
memory non-executable.

This violates the W^X principle, but doesn't seem to be avoidable
for ZTS builds for now. The same problem does not exist for NTS,
as it's a different process executing there, which has it's own
memory protection mapping.

Closes GH-6595.

show more ...

Eliminate redundand comparison insructions

JIT: Update invalid opcache.jit INI value message to include "tracing" and "function" values

`opcache.jit` accepts `tracing` and `function` as aliases, but they were not mentioned in the sta

JIT: Update invalid opcache.jit INI value message to include "tracing" and "function" values

`opcache.jit` accepts `tracing` and `function` as aliases, but they were not mentioned in the start-up INI warning message.
This updates the error message to include all possible values.

Closes GH-6490.

show more ...

Perform early guard type check for result of FETCH_CONSTANT