<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gcc on *scratch*</title>
    <link>https://www.scrivano.org/tags/gcc/</link>
    <description>Recent content in Gcc on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/gcc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Brainfuc**d brainf**k</title>
      <link>https://www.scrivano.org/2016/05/11/brainfucd-brainfk/</link>
      <pubDate>Wed, 11 May 2016 21:15:43 +0000</pubDate>
      <guid>https://www.scrivano.org/2016/05/11/brainfucd-brainfk/</guid>
      <description>&lt;p&gt;Every programmer at some point gets in touch with the Brainfuck programming language and how surprising is that very few instructions are needed to have a Turing complete language, 6 is the case of Brainfuck (plus other 2 for I/O operations). The language operates on a tape of memory cells using only increment, decrement, pointer movement, and conditional loop instructions. Writing a GCC frontend for it turns out to be a manageable project, and the result is a good template for understanding how language frontends hook into the GCC middle-end and optimization passes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
