<?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>Inline on Tenu Tech Brief</title>
    <link>https://cluster-site.onrender.com/tags/inline/</link>
    <description>Recent content in Inline on Tenu Tech Brief</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Feb 2026 09:33:42 +0000</lastBuildDate>
    <atom:link href="https://cluster-site.onrender.com/tags/inline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About inline asm instruction order</title>
      <link>https://cluster-site.onrender.com/posts/about-inline-asm-instruction-order/</link>
      <pubDate>Wed, 25 Feb 2026 09:33:33 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/about-inline-asm-instruction-order/</guid>
      <description>• I wonder if there is a method to preserve the order of instructions from inline assembly relative to other statements. • According to Extended Asm (Using the GNU Compiler Collect</description>
    </item>
    <item>
      <title>Inline asm: canonicalizer does not respect `i` and `d` constraints</title>
      <link>https://cluster-site.onrender.com/posts/inline-asm-canonicalizer-does-not-respect-i-and-d-constraints/</link>
      <pubDate>Sat, 21 Feb 2026 00:36:15 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/inline-asm-canonicalizer-does-not-respect-i-and-d-constraints/</guid>
      <description>• Given the following LLVM MLIR dialect example (example.mlir ): llvm.func @f(%arg0: i16) { %0 = llvm.mlir.constant(64 : i16) : i16 %1 = llvm.mlir.constant(32 : i16) : i16 %5 = llv</description>
    </item>
    <item>
      <title>Which doc format to use? Inline Doxygen/rst/markdown</title>
      <link>https://cluster-site.onrender.com/posts/which-doc-format-to-use-inline-doxygen/rst/markdown/</link>
      <pubDate>Wed, 18 Feb 2026 15:28:32 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/which-doc-format-to-use-inline-doxygen/rst/markdown/</guid>
      <description>• I&amp;rsquo;m a bit confused that we have 3 ways of documenting this. • In particular, I want to document a somewhat complicated API - that to be used correctly - one needs to apply change</description>
    </item>
  </channel>
</rss>
