<story><title>I wrote a 231-byte Brainfuck compiler by abusing everything</title><url>https://briancallahan.net/blog/20210710.html</url></story><parent_chain></parent_chain><comment><author>panic</author><text>Here&amp;#x27;s an even smaller one for 64-bit Linux: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;ianh&amp;#x2F;61e6219f0a9866b31a2b864033c1812e&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;ianh&amp;#x2F;61e6219f0a9866b31a2b864033c1812...&lt;/a&gt;&lt;p&gt;&lt;pre&gt;&lt;code&gt;    $ uname -a
    Linux personal-1 4.19.0-6-cloud-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64 GNU&amp;#x2F;Linux
    $ as -g -o bf.o bf.S &amp;amp;&amp;amp; ld -o bf bf.o
    $ size bf.o
       text    data     bss     dec     hex filename
        167       0       0     167      a7 bf.o
    $ size bf
       text    data     bss     dec     hex filename
        199       0       0     199      c7 bf&lt;/code&gt;&lt;/pre&gt;</text></comment>
<story><title>I wrote a 231-byte Brainfuck compiler by abusing everything</title><url>https://briancallahan.net/blog/20210710.html</url></story><parent_chain></parent_chain><comment><author>xg15</author><text>a 231-byte Brainfuck-to-C compiler*&lt;p&gt;It&amp;#x27;s still an impressive feat, and very informative on the assembly details - but doesn&amp;#x27;t feel as incredible as the headline makes believe as the core logic seems to be a string search-and-replace of the strings in the &amp;quot;reviewing brainfuck&amp;quot; table.&lt;p&gt;Seems to me, you could write the next brainfuck compiler in sed.</text></comment>