<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Abi on ./Code</title><link>https://blog.ouankou.com/tags/abi/</link><description>Recent content in Abi on ./Code</description><generator>Hugo</generator><language>en-US</language><copyright>© Anjia Wang</copyright><lastBuildDate>Mon, 04 May 2026 00:56:32 -0700</lastBuildDate><atom:link href="https://blog.ouankou.com/tags/abi/index.xml" rel="self" type="application/rss+xml"/><item><title>How REX Made Literal Scalar Target Parameters Match The Modern OpenMP Launch ABI</title><link>https://blog.ouankou.com/2026/04/24/how-rex-made-literal-scalar-target-parameters-match-the-modern-openmp-launch-abi/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.ouankou.com/2026/04/24/how-rex-made-literal-scalar-target-parameters-match-the-modern-openmp-launch-abi/</guid><description>&lt;p&gt;The previous post fixed the rules around launch geometry. REX may use source-level tripcount knowledge to improve compiler-owned launch defaults, but it must not silently rewrite explicit user launch clauses just to win a benchmark.&lt;/p&gt;
&lt;p&gt;That made the next performance layer easier to see.&lt;/p&gt;
&lt;p&gt;Once the launch shape is fair, the generated host still has to describe the target region to the OpenMP offload runtime. That description includes every argument:&lt;/p&gt;</description></item></channel></rss>