Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.

```c
static int my_method_call_handler(zend_execute_data *execute_data)
{
	zend_printf("hello\n"); // <-- No call
	return ZEND_USER_OPCODE_DISPATCH;
}

static PHP_MINIT_FUNCTION(phalcon)
{
	zend_set_user_opcode_handler(ZEND_INIT_METHOD_CALL, my_method_call_handler);
}
```
```php
$class = "string";
$class->test();
```
php.ini:
```ini
opcache.enable=1
; 启用 Zend OPCache，在 CLI 模式下 
opcache.enable_cli=1
```
no output.

Hi Dreamsxin,

I find it hard to understand this bug report.

I can see you are using an extension with the name Phalcon - but my understanding is that Phalcon itself is not compatible with PHP 8 yet: https://github.com/phalcon/cphalcon/issues/15186

It may be better to talk to the Phalcon people and explain what problem you're having with them, or just wait for Phalcon to support PHP 8.

Otherwise, we would probably need more details of what you are attemting, why you think it should work, and why you think it's a problem to be fixed in PHP.

`run php test.php`

Normally, should be output : hello

Hook `ZEND_INIT_METHOD_CALL`, call `zend_printf("hello\n");`

But, it not work.

Like this extension, https://github.com/nikic/scalar_objects
When disable opcache work fine.
But enable can't work.

@dmitry: I'm wondering whether we should respect user opcode handlers in JIT. It seems like it should be possible, but maybe user opcode handlers break assumptions by type inference etc.

I think we shouldn't support user opcode handlers in JIT.

I don't see a way to handle all possible return values (e.g 
ZEND_USER_OPCODE_DISPATCH) and ability to jump (change EX(opline)).

In general, for each user opcode handler, we may transfer control to interpreter.

That makes sense. Just not JITing when a user opcode handler is involved seems reasonable.

Fixed by d5a82e2c4eebe8337ff7790db46d812af2fbcec9