Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92062 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65251 invoked from network); 1 Apr 2016 14:43:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2016 14:43:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=xinchen.h@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.181 as permitted sender) X-PHP-List-Original-Sender: xinchen.h@zend.com X-Host-Fingerprint: 209.85.213.181 mail-ig0-f181.google.com Received: from [209.85.213.181] ([209.85.213.181:38674] helo=mail-ig0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 32/22-42107-E198EF65 for ; Fri, 01 Apr 2016 09:43:43 -0500 Received: by mail-ig0-f181.google.com with SMTP id ui10so14613916igc.1 for ; Fri, 01 Apr 2016 07:43:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FE+eb7Jy7QyfIBlRALHOvcWngZPROWRMxpSmJuX+pMc=; b=HkoAEREG8jmhrLhvV6wMAZSAlJbdek/iY80/PVyT3JdQj0KgyMGoeSKyh8DOR+Om59 WZuGHEOiPpC0TWKh1dtRxPzkvMXT/ln2Isutj53uW0/k8whEfqNITdGGcu39+UAlros9 1dbdd1ar6pJsAXaSfQT2NS6elVindgEQj3Qn2EnkPYCB+PeG/QNFaJZAb2rWp1kMLSMa BeP1QXaFofDPQLm/SaflWhxgx7FIZHddH0khbnpWaTgkO/0Dnjq+UXcOyVMKWF+QL3f1 V55ACAbWvZk8Va5akUZOTn0tNFPmU6Di30vzr3r1sJj7iOnh8mhfPOGQAAAvsaU+gveL 93Ew== X-Gm-Message-State: AD7BkJL/eY24of519z7gvH1FLDp8lRJ8eg9RoF+d9JRWb31vqvTb2uuYZK8xLj0m7Jo6abEr X-Received: by 10.50.65.106 with SMTP id w10mr3948080igs.3.1459521819581; Fri, 01 Apr 2016 07:43:39 -0700 (PDT) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id f89sm5871794ioj.31.2016.04.01.07.43.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Apr 2016 07:43:38 -0700 (PDT) Received: by mail-io0-f175.google.com with SMTP id g185so154943344ioa.2 for ; Fri, 01 Apr 2016 07:43:38 -0700 (PDT) X-Received: by 10.107.34.201 with SMTP id i192mr8753454ioi.161.1459521817782; Fri, 01 Apr 2016 07:43:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.15.77 with HTTP; Fri, 1 Apr 2016 07:43:18 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Apr 2016 22:43:18 +0800 X-Gmail-Original-Message-ID: Message-ID: To: Lin Yo-An Cc: Dmitry Stogov , internals , Nikita Popov Content-Type: multipart/alternative; boundary=001a1140e10c7dd6bc052f6d671b Subject: Re: [PHP-DEV] Object getter method optimization From: laruence@php.net (Xinchen Hui) --001a1140e10c7dd6bc052f6d671b Content-Type: text/plain; charset=UTF-8 Hey: On Fri, Apr 1, 2016 at 4:35 PM, Lin Yo-An wrote: > Hi Dmitry, Nikita, Andrea > > > My implementation now is able to get the property offset and fetch object > property directly without invoking zend_std_read_property and pushing new > call frame onto the stack. > > The current behavior: > > 1. In compile-time, the pass_two() function now marks the getter functions > in op_array.accessor.type > > 2. When Zend Engine first time attempt to read the property, it saves the > property offset in the accessor field and mark the method as a "getter". > I am not sure if I understand you correctly, but.. have you consider this case? a; } else { return $this->b; } } } $a = new A(); echo $a->nomeaning; echo $a->nomeaning; ?> thanks > > 3. When Zend Engine second time invoke the getter method, it checks the > accessor field and try to read the property value directly instead a > "method call" > > > > The implementation did some change: > > 1. Added accessor struct to op_array to save "accessor" related > information (getter or setter, property offset) > > 2. Added two statement in zend_std_read_property to save property offset. > > 3. Added op code check in zend_compile (The pass_two() function) to mark a > function is a getter) > > > But now I encountered a problem, I can't store the result value in > INIT_METHOD_CALL op, the result var is only available in DO_FCALL_* > > > > I have an idea for solving this, but I'm not sure if it's good or not: > > > If DO_FCALL_* will always follow a INIT_METHOD_CALL, then I think we can > store result var from the next op (DO_FCALL) and skip DO_FCALL directly. > > > Would be great if I can have your advices and suggestion. :-) > > > Thanks, Yo-An Lin > > > > > > > > > > > > > > > > > > > On Tue, Mar 22, 2016 at 4:45 PM, Dmitry Stogov wrote: > >> Hi Yo-An Lin, >> >> >> This "run-time inlining" approach may work. >> >> >> PHP compiler (or optimizer) may mark functions and methods suitable for >> "run-time" inlining (e.g. methods without arguments and FETCH_OBJ_R UNUSED, >> CONST -> TMP; RETURN TMP). >> >> Then INIT_METHOD_CALL may check this flag and execute "optimized code >> sequence" instead of pushing stack frame and real call. >> >> >> However, I'm not sure what kind of performance impact this may make, >> because we will have to make additional check on each INIT_METHOD_CALL >> execution. >> >> >> Thanks. Dmitry. >> >> >> ------------------------------ >> *From:* Lin Yo-An >> *Sent:* Saturday, March 19, 2016 10:08 >> *To:* Dmitry Stogov >> *Cc:* internals; Xinchen Hui >> *Subject:* Re: [PHP-DEV] Object getter method optimization >> >> Hi Dmitry, >> >> >> Thanks for your reply! You're correct. let me try to explain your points: >> >> If I have a main.php and worker.php >> >> And I defined work($worker) { $status = $worker->getStatus(); } inside >> main.php >> >> when main.php is compiled, we don't know what the class entry of $worker >> is. What we only know is invoking a method "getStatus" on $worker CV unless >> we know we have to compile worker.php before main.php and add a type hint >> on $worker. >> >> Is it correct? >> >> >> Since the original approach doesn't work, here comes another new idea: >> >> When executing method call on an object, if we found the method body are >> just 2 op codes (FETCH_OBJ_R and RETURN), we then denote the method is a >> "getter method" >> >> And the next time, when we execute the same method, we found the "getter >> method" flag, we simply execute FETCH_OBJ_R on that object and return the >> value to avoid extra op code execution time. >> >> Do you think if this could work? >> >> >> >> >> Best Regards and Thanks for your work on PHP VM >> Yo-An Lin >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Mar 18, 2016 at 3:36 PM, Dmitry Stogov wrote: >> >>> Hi Yo-An Lin, >>> >>> Unfortunately, this approach won't work. >>> At first, at compile time we don't know the body of called getter. >>> At second, the called method might be changed even at run-time, because >>> of polymorphism. >>> >>> Tricks like this might be implemented using JIT and polymorphic inline >>> caches. >>> >>> Thanks. Dmitry. >>> >>> ________________________________________ >>> From: Lin Yo-An >>> Sent: Friday, March 18, 2016 05:23 >>> To: internals >>> Subject: [PHP-DEV] Object getter method optimization >>> >>> Hello Everyone, >>> >>> >>> I am recently trying to write an optimizer that could optimize the getter >>> method call into just one object fetch opcode. >>> >>> I'd like to know thoughts from you guys, here is the note: >>> https://c9s.hackpad.com/INLINE-OP-TVGo9WcshbZ >>> >>> -- >>> Best Regards, >>> >>> Yo-An Lin >>> https://github.com/c9s >>> >> >> >> >> -- >> Best Regards, >> >> Yo-An Lin >> > > > > -- > Best Regards, > > Yo-An Lin > -- Xinchen Hui @Laruence http://www.laruence.com/ --001a1140e10c7dd6bc052f6d671b--