RE: [PHP-DEV] Re: Zend JIT Open Sourced
| From: | Zeev Suraski | Date: | Tue, 03 Mar 2015 15:26:50 +0000 |
| Subject: | RE: [PHP-DEV] Re: Zend JIT Open Sourced | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-84241@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: julienpauli@gmail.com [mailto:julienpauli@gmail.com] On Behalf Of
> Julien Pauli
> Sent: Tuesday, March 03, 2015 5:11 PM
> To: Zeev Suraski
> Cc: Anthony Ferrara; PHP Internals
> Subject: Re: [PHP-DEV] Re: Zend JIT Open Sourced
>
> On Tue, Mar 3, 2015 at 2:05 PM, Zeev Suraski <zeev@zend.com> wrote:
>
>
> > So I do apologize to the person. I don't to the code.
>
> I wanted to verify whether my gut was correct (minimal amount of
> output, and
> stdout is in fact buffered - output shouldn't move the needle) and
> asked
> Dmitry to rerun the C test on the same system, but this time with the
> output
> code completely commented out:
> real 0m0.011s (+- 0.01)
> user 0m0.011s (+- 0.01)
> sys 0m0.001s
>
> Apologies to the code might be in order :)
>
> The source of the JIT engine's edge is, as Dmitry and Andi said, the
> CPU-specific optimizations that gcc -O2 doesn't generate, and
> therefore it
> can actually be faster than a generic native executable in some (I
> would
> guess not all that common) cases.
>
>
>
> That's why one may run GCC -march=native when mastering the hardware.
> I guess here, no JIT can outperform that.
Of course, but the vast majority of people don't build their own binaries.
internals@ audience may not be the best sample to gauge that percentage,
though :)
Zeev