PROTECTED]
Sent: Friday, March 14, 2008 8:24 PM
To: Stas Malyshev
Cc: Dmitry Stogov; Andi Gutmans; phpxcache; internals@lists.php.net
Subject: Re: [PHP-DEV] Patch for opcode caches
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
But that means we are compiling inheritance when
2008 8:24 PM
>> To: Stas Malyshev
>> Cc: Dmitry Stogov; Andi Gutmans; phpxcache; internals@lists.php.net
>> Subject: Re: [PHP-DEV] Patch for opcode caches
>>
>>
>> Hello Stanislav,
>>
>> Friday, March 14, 2008, 5:51:49 PM, you wrote:
>>
The patch has been just committed.
You should use something like the following code to make it work.
function cache_compile_file($filename) {
if (!is_cached($filename)) {
...
orig_compiler_options = CG(compiler_optins);
CG(compiler_
session (or caused by TSRM/ZendEngine) seems broken in my local cvs
checkout i'm not sure if it's relatived to this patch but i did 'cvs
up' and some commit broke the patch (with conflicts)
please commit, or roll out another diff against the PHP_5_3 cvs so i
can test it again
thanks
--
PHP Inter
> -Original Message-
> From: Marcus Boerger [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 9:28 PM
> To: Stas Malyshev
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode caches
>
>
> Hello Stanislav,
>
> Friday, Marc
Keeping it seems fairly meaningless (it was a temporary hack anyway).
Since 5.1 (or possibly even late 5.0) releases much of the new
functionality ignores it anyway.
On 14-Mar-08, at 11:23 AM, Derick Rethans wrote:
On Fri, 14 Mar 2008, Dmitry Stogov wrote:
however in
PHP_5_3 we even keep
> -Original Message-
> From: Marcus Boerger [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 8:24 PM
> To: Stas Malyshev
> Cc: Dmitry Stogov; Andi Gutmans; phpxcache; internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode caches
>
>
> H
> -Original Message-
> From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 10:11 PM
> To: Rasmus Lerdorf
> Cc: Marcus Boerger; Dmitry Stogov; Andi Gutmans;
> internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode cac
> -Original Message-
> From: Xuefer [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 15, 2008 11:21 AM
> To: Rasmus Lerdorf
> Cc: Marcus Boerger; Stas Malyshev; Dmitry Stogov; Andi
> Gutmans; internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode cach
> I don't actually see early binding as being much of a problem, the real
> problem is when the same class is both early and late bound. If you
> consistently always bind early or always bind late, opcode caches should
> be quite happy to let you do that. But if you mix the two, things get
>
I don't actually see early binding as being much of a problem, the real
problem is when the same class is both early and late bound. If you
consistently always bind early or always bind late, opcode caches should
be quite happy to let you do that. But if you mix the two, things get
That's w
Hello Stanislav,
Friday, March 14, 2008, 6:48:52 PM, you wrote:
> Hi!
>> Lemme just think, doing inheritance at compile time before we send the stuff
>> to an opcode cache can be slower then? How is that possible? After all late
>> binding means we do it at run time. And no matter how much faste
Marcus Boerger wrote:
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If ther
Hello Pierre,
yep, stupid me. I got confused by your wording :-)
marcus
Friday, March 14, 2008, 4:42:32 PM, you wrote:
> On Fri, Mar 14, 2008 at 4:22 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>> Hello Pierre,
>>
>> it is unused code that does not work as intended and causes trouble. And
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
>> But that means we are compiling inheritance when a file is loaded form
>> the cache. The goal should be to compiling inheritance when writing to
>> the opcode cache file. All we achieve here is a slow down. If there is
> You can
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If there is
You can not do that. You do not know that until runtime.
something that makes thi
Hello Dmitry,
Friday, March 14, 2008, 5:08:18 PM, you wrote:
>> I do not want to remove early binding. In fact I always
>> wanted to have early binding as much as possible. Because
>> that is faster and makes compiler caches easier. So why slow
>> down stuff? A Compiler cache wants everythign
> I do not want to remove early binding. In fact I always
> wanted to have early binding as much as possible. Because
> that is faster and makes compiler caches easier. So why slow
> down stuff? A Compiler cache wants everythign as static as
> possible which means a compiler cache wants early b
On Fri, Mar 14, 2008 at 4:22 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Pierre,
>
> it is unused code that does not work as intended and causes trouble. And
> at leats it makes maintanance harder. So that is a very big reason to drop
> it.
Yes, I fully agree (you may have missed the
hpxcache; internals@lists.php.net
>> Subject: Re: [PHP-DEV] Patch for opcode caches
>>
>>
>> Hello Dmitry,
>>
>> Monday, March 10, 2008, 1:48:05 PM, you wrote:
>>
>> > Hi Marcus,
>>
>> >> > -Original Message-
>> >
On Fri, 14 Mar 2008, Dmitry Stogov wrote:
> however in
> PHP_5_3 we even keep ze1_compatibility_mode.
> I'm not able to remove it.
WHy not? It's quite broken anyway.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
--
PHP Internals - PHP Runtime
Hello Pierre,
it is unused code that does not work as intended and causes trouble. And
at leats it makes maintanance harder. So that is a very big reason to drop
it.
marcus
Friday, March 14, 2008, 11:11:06 AM, you wrote:
> On Fri, Mar 14, 2008 at 11:06 AM, Hannes Magnusson
> <[EMAIL PROTECTED
On Fri, Mar 14, 2008 at 11:06 AM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
> On Fri, Mar 14, 2008 at 9:46 AM, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
> >
> > Removing early-binding at all might be a subject for PHP6, however in
> > PHP_5_3 we even keep ze1_compatibility_mode.
>
> http://n
On Fri, Mar 14, 2008 at 9:46 AM, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
>
> Removing early-binding at all might be a subject for PHP6, however in
> PHP_5_3 we even keep ze1_compatibility_mode.
http://news.php.net/php.internals/36085
-Hannes
--
PHP Internals - PHP Runtime Development Mailing
Hi Marcus,
> -Original Message-
> From: Marcus Boerger [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 13, 2008 9:27 PM
> To: Dmitry Stogov
> Cc: Andi Gutmans; Stas Malyshev; phpxcache; internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode caches
&g
hans; internals Mailing List; Andi Gutmans; Stas
>> > Malyshev; phpxcache
>> > Subject: Re: [PHP-DEV] Patch for opcode caches
>> >
>> > Hello Dmitry,
>> >
>> > please don't apply. The patch looks rather rough and untested (see
>> > b
omments about
compiler options)
Thanks. Dmitry.
> -Original Message-
> From: Dmitry Stogov
> Sent: Monday, March 10, 2008 3:48 PM
> To: 'Marcus Boerger'
> Cc: Andi Gutmans; Stas Malyshev; 'phpxcache';
> 'internals@lists.php.net'
> Subject
Hi!
This does not work.
Does not work either.
And this does also not work.
The reason is that you did not update the table that allows those
Which table are you referring to?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PR
Hi Marcus,
> > -Original Message-
> > From: Marcus Boerger [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, March 09, 2008 3:00 PM
> > To: Dmitry Stogov
> > Cc: Derick Rethans; internals Mailing List; Andi Gutmans; Stas
> > Malyshev; phpxcache
> &g
Hi phpxcache,
On 08/03/2008, phpxcache <[EMAIL PROTECTED]> wrote:
> all test cases that pass without XCache now pass
> with XCache too.
Are these tests that are already in the cvs repository? If not, it
would be great to get them in. Sounds like they could be useful
whether or not the patch gets
On Mon, Mar 10, 2008 at 5:59 AM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Dmitry,
>
> please don't apply. The patch looks rather rough and untested (see below).
> Also I really disagree to making the engine even more complex and adding
> even more different behavior ways. That way we ju
Hello Dmitry,
please don't apply. The patch looks rather rough and untested (see below).
Also I really disagree to making the engine even more complex and adding
even more different behavior ways. That way we just introduce more errors
as we cannot test the engine in all its modes. We simply do no
checked and it works, all test cases that pass without XCache now pass
with XCache too. i'll commit after your commit in ZendEngine
thanks
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 7 Mar 2008, Dmitry Stogov wrote:
> The attached patch for PHP_5_3 is going to provide general solution to
> control some aspects of PHP compilation. It is absolutely necessary for
> all opcode caches to make cached scripts work exactly in the same way as
> non-cached.
There's no attached
Hi,
The attached patch for PHP_5_3 is going to provide general solution to
control some aspects of PHP compilation. It is absolutely necessary for
all opcode caches to make cached scripts work exactly in the same way as
non-cached.
The problem occurs because early binding of inherited classes is n
35 matches
Mail list logo
