<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Jit on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/jit/</link>
    <description>Recent content in Jit on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jul 2013 14:11:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/jit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JVM JIT Compilation: What the C2 Compiler Does to Your Loops</title>
      <link>https://blog.turboawesome.win/2013/07/jvm-jit-compilation-what-the-c2-compiler-does-to-your-loops/</link>
      <pubDate>Tue, 30 Jul 2013 14:11:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2013/07/jvm-jit-compilation-what-the-c2-compiler-does-to-your-loops/</guid>
      <description>The HotSpot C2 compiler can transform your Java bytecode into surprisingly efficient native code — but only under specific conditions. Understanding those conditions explains a class of mysterious performance cliffs.</description>
    </item>
  </channel>
</rss>
