<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>C-Programming on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/c-programming/</link>
    <description>Recent content in C-Programming on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/c-programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TCC vs chibicc vs cproc in 2026: Which Tiny C Compiler Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-24-tcc-vs-chibicc-vs-cproc-tiny-c-compilers/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-24-tcc-vs-chibicc-vs-cproc-tiny-c-compilers/</guid>
      <description>&lt;p&gt;Every C developer has felt it: you change one line, and the build system grinds for ninety seconds to reprocess a dependency graph you have not touched since Tuesday. Full toolchains like GCC and Clang are engineering marvels, but they are also enormous — hundreds of megabytes of binaries carrying decades of optimization passes you did not ask for on an edit-compile-run loop.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
