> -----Original Message----- > From: julienpa...@gmail.com [mailto:julienpa...@gmail.com] On Behalf Of > Julien Pauli > Sent: Monday, March 02, 2015 9:07 PM > To: Dmitry Stogov > Cc: Bob Weinand; Xinchen Hui; PHP Internals > Subject: Re: [PHP-DEV] Re: About optimization for compiler > > As OPCache is nowadays not compatible at all with PHP7 (development has > not started yet, or I'm not aware of it) , why not merge OPCache to PHP7 > source tree (when the time for this will come), still as an extension at > first > time, and keep developing optimizer passes into this (aka : not in Zend/) > ?
It's a bit OT, but can you explain what you mean here? OPcache works with the current master (PHP 7), and actually, OPcache worked with phpng all along and definitely since it was merged into master... It's been integrated to the php-src tree since it became standard in 5.5. Do you mean the standalone github repos for older versions? > I'm also +1 to keep our optimizations into OPCache (into an extension), I'm slightly confused - you mean keep it in (or move optimization over to) the OPcache extension, or move it into its own extension? If it's the former, then I agree. Optimization passes and opcode caching are very much linked, as performing optimizations without having an opcode cache rarely makes sense. > and > allow them to be disabled (like its the case actually), because this > subject is > very hot and sensible. > > We should keep a PHP compiler as-is, and move optimization passes away > from it. zend_extension_op_array_handler() callback is designed for that > purpose. Agreed. Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
