<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on ./Code</title><link>https://blog.ouankou.com/tags/performance/</link><description>Recent content in Performance on ./Code</description><generator>Hugo</generator><language>en-US</language><copyright>© Anjia Wang</copyright><lastBuildDate>Thu, 16 Apr 2026 23:15:19 -0700</lastBuildDate><atom:link href="https://blog.ouankou.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>How REX Lowers Target Loops Into Direct GPU Kernels</title><link>https://blog.ouankou.com/2026/04/06/how-rex-lowers-target-loops-into-direct-gpu-kernels/</link><pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.ouankou.com/2026/04/06/how-rex-lowers-target-loops-into-direct-gpu-kernels/</guid><description>&lt;p&gt;The previous posts in this series covered two neighboring stages of GPU lowering:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;how REX outlines a target region into a real device kernel,&lt;/li&gt;
&lt;li&gt;and how the host side builds launch packets and runtime map arrays for that kernel.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There is still one very important step in between those two stories:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;what happens to the actual &lt;code&gt;for&lt;/code&gt; loop inside the outlined kernel body?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That step matters more than it first sounds.&lt;/p&gt;</description></item><item><title>How REX Validates GPU Offloading With Real Benchmarks</title><link>https://blog.ouankou.com/2026/04/05/how-rex-validates-gpu-offloading-with-real-benchmarks/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.ouankou.com/2026/04/05/how-rex-validates-gpu-offloading-with-real-benchmarks/</guid><description>&lt;p&gt;The previous post in this series covered the semantic checkpoint before GPU execution: &lt;code&gt;lowering_cpu&lt;/code&gt; runs the original OpenMP program and the REX-lowered program on the same CPU runtime and asks whether the transformation still preserves meaning.&lt;/p&gt;
&lt;p&gt;That is a strong test layer.&lt;/p&gt;
&lt;p&gt;It is still not the last one.&lt;/p&gt;
&lt;p&gt;At some point the compiler has to survive the real thing:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a real application,&lt;/li&gt;
&lt;li&gt;real offloading,&lt;/li&gt;
&lt;li&gt;real runtime glue,&lt;/li&gt;
&lt;li&gt;real device launches,&lt;/li&gt;
&lt;li&gt;real numerical output,&lt;/li&gt;
&lt;li&gt;and real performance scrutiny.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is the benchmark-validation layer.&lt;/p&gt;</description></item></channel></rss>