5.5.18 now
Update LSAPI to 6.7, added support for 'filter_input'.
Fixed a crash in CLI mode.
Update LSAPI to 6.7, added support for 'filter_input'.
Fixed a crash in CLI mode.
Merge branch 'PHP-5.5' of git.php.net:php-src into PHP-5.5
Fix ext/xml warnings
Fix $x .= $x

Also add a nice comment pointing out that concat runs on magic.
Release memory for PDO Stmt ctor args
Added test case to complement commit 29397f8
According to LSB 3.2, finite() has been deprecated with C99.

See: https://refspecs.linuxfoundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/baselib-finite.html

Changed the order in which we detect whether to use finite() or isfinite(), favouring the latter.
Move safe_address into zend_multiply.h

This allows reuse in zend_arena_calloc.

Also renamed the function to zend_safe_address as it's no longer
private to the allocator.
Revert "Move safe_address into zend_multiply.h"

This reverts commit 43b02e169c718335a82b8c90c3252194f988659a.

I'm getting symbol resolution issues for zend_error_noreturn in the
opcache.so, so reverting this for now.
fix 64 bit string index usage
fixed string index handling with references
fixed the tests, related to the basename behaviour, bug #66395
fix null pointer deref
Fixed comments and removed useless code.
Removed IS_STR_OFFSET type and corresponding macros. Optimized string offset handling in ASSIGN_DIM opcode.
Fix parser stack destruction with dummy ENCAPSED_AND_WHITESPACE

T_ENCAPSED_AND_WHITESPACE is now specified to always hold a value,
so give it a NULL value in the dummy cases.
Added ability to make a number of "warmup" requests before an actual benchmark.
(php-cgi -T [<number-of-warmup-requests>,]<number-of-benchmark-requests> <file>)
made Visual Studio to understand that zend_error_noreturn() will not return

- windows only, on linux gcc would cause a warning that the function returns,
  as no noreturn functions are used
- ZEND_NORETURN works on windows as well now, using __declspec(noreturn),
  which is useful for the other cases
- one more function call will be needed, which is not critical for the
  error reporting
- the way is open to enable the same for gcc as soon as it's not causing a warning