<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 18 Jun 2013 17:41:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Jacob Santos' Blog: Would PHP benefit from JIT compilation?]]></title>
      <guid>http://www.phpdeveloper.org/news/7513</guid>
      <link>http://www.phpdeveloper.org/news/7513</link>
      <description><![CDATA[<p>
In <a href="http://www.santosj.name/programming/php-related/php/would-php-benefit-from-jit-compilation/">this post</a> from his blog, <i>Jacob Santos</i> asks the question "would PHP benefit from JIT compilation?" 
</p>
<p>
JIT (just in time) compilation is, according to <a href="http://en.wikipedia.org/wiki/Just-in-time_compilation">Wikipedia</a>, a method for converting, at runtime, code from one format into another, for example bytecode into native machine code. To try to see the benefit of this, <i>Jacob</i> asks four questions in his post (each with their own problems):
<ul>
<li>Q: What advantage over opcode caching is gained?<br/>
P: A JIT library that works with PHP would have to support all of the architectures that PHP can run on!
<li>Q: Which JIT library is the best one?<br/>
P: A JIT compiler is not going to achieve anything without either storing the results or caching them.
<li>Q: Wouldn't writing PHP extensions negate the need for JIT compilation?
<li>Q: When will I develop and release my implementation?
</ul>
Check out <a href="http://www.santosj.name/programming/php-related/php/would-php-benefit-from-jit-compilation/#comments">the comments</a> for some great thoughts from others about this kind of compilation.
</p>]]></description>
      <pubDate>Tue, 27 Mar 2007 10:52:00 -0500</pubDate>
    </item>
  </channel>
</rss>
