Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80347
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <000a01d02cf8$ab090130$011b0390$@tekwire.net>
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
	<CAEZPtU5M_NdtZ-e_48Ce5Rjb1KKHkzDMrqLD5sx-WwDctR7u5Q@mail.gmail.com>
	<001501d02ccc$574a6bf0$05df43d0$@tekwire.net>
	<CAEZPtU73+y4AJ9BfACmYuBe79+Ls-A-yQSZhxUoTi3m8KTQEMQ@mail.gmail.com>
	<000a01d02cf8$ab090130$011b0390$@tekwire.net>
Date: Sat, 10 Jan 2015 19:06:21 -0800
Message-ID: <CAEZPtU5ShKa9bMUOKsSuKjmEcXQZhsEUWrwNmsj2a_VSKSizEw@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>, 
	Derick Rethans <derick@php.net>, Dmitry Stogov <dmitry@zend.com>, Laruence <laruence@php.net>
Cc: PHP internals <internals@lists.php.net>, Benjamin Eberlei <kontakt@beberlei.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: pierre.php@gmail.com (Pierre Joye)

On Sat, Jan 10, 2015 at 9:12 AM, Fran=C3=A7ois Laupretre
<francois@tekwire.net> wrote:
> De : Pierre Joye [mailto:pierre.php@gmail.com]
>
>> Opcache is why I think we should have a list registered names. A simple =
hash exists and the cache will know what to do.
>
> Sorry, I am not sure I understand how the opcode cache, as it exists now,=
 can understand this. Do you mean that opcode cache code would need to be m=
odified ?

Yes and no. Yes if we want them to do not even try to update files
that are statically built in extensions. And yes, if we want that (for
whatever reasons I cannot think about right now).

> Anyway, that's the occasion to ask this : do we consider opcache the only=
 supported opcode cache in the future or do we still support APC and other =
alternative opcode caches. I'd like to know if we are free to improve the w=
ay opcode cache communicates with the core, or if we must keep BC.

That's PHP7, we can and have already broke BC internally.

Patch now in my fork (finally got a faster connection):

https://github.com/pierrejoye/php-src/compare/php:master...master

Date use as example.

Key are two parts:

. the configure script to create the static data (could actually be
used for any binary data btw)
. the zend_execute_string call, which could happen anywhere where it
could be done, RINIT making more sense right now

As Sara pointed out , persistent opcode would be way better but as far
as I remember it is something very tricky to do (due to how the
address and offset are stored), maybe it changed now for 7, I did not
check that part. In any case the exec_string and the binary to C
scripts will be helpful there too.

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org