Use zval_ptr_dtor_nogc() to free IS_TMP_VAR operands.
Removed ZEND_SWITCH_FREE opcode (ZEND_FREE used instead).

Initial coalesce operator implementation

Removed ZEND_QM_ASSIGN_VAR and ZEND_JMP_SET_VAR opcodes (in PHPNG they did exacly the same as ZEND_QM_ASSIGN and ZEND_JMP_SET)

Implemented builtin instruction for strlen()

Implemented builtin instruction for type check functions - is_*()

Implemented builtin instruction for strlen()

Implement call_user_func() and call_user_func_array() using special opcodes.
In some rare cases it leads to insignificant changes in error messages.

ZEND_SEND_VAR and ZEND_SEND_VAL specialization

Refactored parameter passing mechanism.

In PHP-5.6 and below each argument passed to user function was copies on VM stack twice.
Now we always have ZEND_INIT_FCALL (or simular) opcode th

Refactored parameter passing mechanism.

In PHP-5.6 and below each argument passed to user function was copies on VM stack twice.
Now we always have ZEND_INIT_FCALL (or simular) opcode that pushes "call frame" on top of VM stack.
"Call frame" is actually the same zend_execute_data structure.
All the following ZEND_SEND instructions push arguments on top of the stack in a way that they directly comes into corresponding CV variables of the called frame. Extra arguments are copied at the end of stack frame (after all CV and TMP variables) on function enterance.

There are two minor incompatibilities:
1) It's not allowed to decalre functions redefining arguments e.g. "function foo($a,$a) {}".
2) func_get_arg() and func_get args() return the current value of argument and not the original value that was sent.

show more ...

Introduced new BIND_GLOBAL instraction instead of FETCH_W+ASSIGN_REF pair that caused a lot of useles checks

add T_POW (**) operator

Fixed recognition of the operator

Added opcode, still doing multiply instead of pow()

opcode now always returns int(42)

The right answer, b

add T_POW (**) operator

Fixed recognition of the operator

Added opcode, still doing multiply instead of pow()

opcode now always returns int(42)

The right answer, but always a float

Yanked code from pow() implementation.

Should not handle negative long as exponent ourselves

Added test cases from pow()

Moved precedence higher than '~'

Added GMP operator overloading

Added ZEND_ASSIGN_POW (**=) operator.

Added pow() as a language construct.

Adjusted test cases for changed precedence.

Reduced pow() to shell function around ZEND_API pow_function()

Reduced test case to only contain edge cases
Added overloading test case

Moved unary minus above T_POW

Revert "Added pow() as a language construct."

Bad bad bad idea.

This reverts commit f60b98cf7a8371233d800a6faa286ddba4432d02.

Reverted unary minus behaviour due to previous revert.
Convert arrays to int(0)
Exponent with array as a base becomes int(0)

Rebase against master

Fixed tokenizer test case

show more ...

Implement argument unpacking

RFC: https://wiki.php.net/rfc/argument_unpacking

Bump year

Merge branch 'PHP-5.6' of https://github.com/php/php-src into PHP-5.6

Merge branch 'PHP-5.4' into PHP-5.5

* PHP-5.4:
stop warnings from unused opcode map
- BFN

stop warnings from unused opcode map

Merge branch 'PHP-5.5' into PHP-5.6

Conflicts:
Zend/zend_vm_opcodes.c

Merge branch 'PHP-5.4' into PHP-5.5

Conflicts:
Zend/zend_vm_opcodes.c

Included new .c file in build too

Merge branch 'PHP-5.5' into PHP-5.6

Conflicts:
Zend/zend_vm_opcodes.h

Merge branch 'PHP-5.4' into PHP-5.5

Conflicts:
Zend/zend_vm_opcodes.h

Moved to new file, killing a lot of warnings