Files
ioccc/2005
Landon Curt Noll c78bda6c0f update tarballs due to recent commits
The commit a1c86c8a7a modified
the navigation bars to include "Original C", so all tarballs
had be update, sorry (tm Canada 🇨🇦).  In particular:

The navigation bar for a winning entry now has a "_Original C_" link
(between the ✅ and the Inventory on the right hand side) so that one
may easily view the original C code that was submitted for IOCCC judging.

In addition, a number of other commits since that time
modified other winning entries.

Ran `make update` to perform the above.
2025-08-18 16:30:59 -07:00
..
2025-08-18 16:30:59 -07:00
…
2024-06-07 02:10:24 -07:00
…

Eighteenth International Obfuscated C Code Contest

Standard IOCCC stuff

View the index.html web page for the given winning entry for information on how on how to compile the entry and how to run the winning program. Look at the winning source and try to figure how it does what it does! You may then wish to look at the Author's remarks for even more details.

Some ANSI C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using gcc instead of your local compiler.

This year we included most of the information included by the submitters in the README.md files (that were used to build the index.html web pages).

Historical note:

The IOCCC has a website and now has a number of international mirrors. The primary website can be found at www.ioccc.org.

Historical update:

The IOCCC website once had a number of international mirrors. As of 2020 Dec 29, GitHub serves as the distributed server farm for the IOCCC winner repo that GitHub renders as Official IOCCC website - www.ioccc.org.

Remarks on some of the entries

We believe you will be impressed with this year's winning entries.

In particular:

Remarks on some of the losing entries

There were some outstanding entries that did not win. Unfortunately some very good entries lost because they:

  • depended too much on non-portable side effects in expressions; and/or

  • depended too much on a particular byte order; and/or

  • required the use of a special script, data file or pseudo-machine language that was not supplied with the entry.

We hope the authors of some of those entries will fix and resubmit them for the next IOCCC.

Final Comments

IMPORTANT NOTE: See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. See also the IOCCC FAQ for additional information on the IOCCC.