Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92891
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVrg3vObe-52kGs6+oTsY883_7iuA2G2tAFg9RC69hhTvA@mail.gmail.com>
References: <CAFKaYMpaSLaKd0avU_41UHYt3taovmNYXhRenz+XoZFUZbkf-Q@mail.gmail.com>
	<CAESVnVrg3vObe-52kGs6+oTsY883_7iuA2G2tAFg9RC69hhTvA@mail.gmail.com>
Date: Thu, 28 Apr 2016 19:39:06 +0100
Message-ID: <CAFKaYMq+s0w4uT-9tKpBybPAri0T0KaFmJdti1oUbptGrt3NiQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1146ddaa58075f05318fd7fb
Subject: Re: [PHP-DEV] Inline functions
From: codekestrel@googlemail.com (Dominic Grostate)

--001a1146ddaa58075f05318fd7fb
Content-Type: text/plain; charset=UTF-8

That sounds wicked.  I look forward to benchmarking it and seeing how its
done.
On 28 Apr 2016 6:39 p.m., "Sara Golemon" <pollita@php.net> wrote:

> On Thu, Apr 28, 2016 at 1:21 AM, Dominic Grostate
> <codekestrel@googlemail.com> wrote:
> > As I understand it, the process by which the call stack is updated and
> > scope changed, is quite expensive.  And from tests I can see that
> function
> > calls do actually add a not insignificant overhead to intensive
> repetitive
> > tasks.
> >
> > So how difficult would it be to get the engine to determine if an inline
> is
> > feasible, then skip the fcall init, and dump the a functions opcode emits
> > directly into the current scope?
> >
> I'm actually working on a proof-of-concept of that already.  I've
> already got basic proxy methods getting inlined, and am working up
> through expression methods and trying to resolve scoping with $this
> and non-publics.
>
> I'll publish a branch on github when I have something interesting to share.
>
> -Sara
>

--001a1146ddaa58075f05318fd7fb--