Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Arno Griffioen via COFF <coff@tuhs.org>
To: Computer Old Farts Followers <coff@tuhs.org>
Cc: Arno Griffioen <arno.griffioen@ieee.org>
Subject: [COFF] Re: C compiler in 512 bytes
Date: Thu, 25 May 2023 07:26:19 +0200	[thread overview]
Message-ID: <ZG7xe5h3v9Hw8hil@ancienthardware.org> (raw)
In-Reply-To: <CANCZdfoDO4XA7wcLARMiU9PAK_TJFM_8_DqyP34mM6feSNi5_Q@mail.gmail.com>

On Wed, May 24, 2023 at 06:14:42PM -0600, Warner Losh wrote:
> This appeared in my news feed and hacker news.
> https://xorvoid.com/sectorc.html

Thanks!

I always also loved the obfuscated C contest as you could pick up so much 
neat stuff and low-down info from that. Also showed you a lot of the underlying
behaviour in the C language and how compilers would 'fill in the blanks'
in several cases.

As students during my college time we regularly got into friendly 
competitions to do the 'shoterst source xyz' or 'fastest' or even some
obscure 'smallest resulting ASM from the compiler'. Fun times..

Longest running one I remember was cramming a fully compiling and running
Conway's 'life' into as little C-source bytes as possible (excluding the 
playing field data, but it did have to read that..). I vaguely remember it 
getting down to a ridiculous 30-something bytes or so.

Again.. Thanks for the link. Definite reading material for a quiet moment..

							Bye, Arno.

      parent reply	other threads:[~2023-05-25  5:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  0:14 [COFF] " Warner Losh
2023-05-25  0:47 ` [COFF] " Larry McVoy
2023-05-25  1:06 ` Clem Cole
2023-05-25  6:30   ` Lars Brinkhoff
2023-09-06 11:29   ` Paul Guertin
2023-05-25  5:26 ` Arno Griffioen via COFF [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZG7xe5h3v9Hw8hil@ancienthardware.org \
    --to=coff@tuhs.org \
    --cc=arno.griffioen@ieee.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).