<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Interesting Things &#187; Just-in-time compilation</title>
	<atom:link href="http://www.bradshawenterprises.com/blog/tag/just-in-time-compilation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bradshawenterprises.com/blog</link>
	<description>Richard Bradshaw&#039;s idea of what is interesting</description>
	<lastBuildDate>Mon, 24 May 2010 19:17:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Benchmarking Chrome&#8217;s V8 Javascript engine</title>
		<link>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 18:28:24 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Benchmark]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Just-in-time compilation]]></category>
		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=116</guid>
		<description><![CDATA[Having previously looked at the memory usage of Google&#8217;s Chrome, it&#8217;s time to analyse it&#8217;s much mentioned javascript engine, V8. Assumedly named after the engine with the same name, V8 compiles javascript to machine code, rather than bytecode to achieve greater performance. In this respect, it&#8217;s similar to Firefox 3.1&#8242;s TraceMonkey, a JIT javascript compiler again [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
