Logo by winner Matt Zucker
The International Obfuscated C Code
[ The judges |
IOCCC home page |
How to enter |
IOCCC news |
People who have won |
Winning entries ]
The source winners of the 27th IOCCC have been released. Congratulations!
The IOCCC is currently CLOSED.
Right now, you CANNOT register as a contestant with the IOCCC,
nor can you submit an entry because the IOCCC is yet NOT open.
Please see the watch the IOCCC news below for information on the next IOCCC.
Goals of the Contest
- Obfuscate: tr.v. -cated, -cating, -cates.
- To render obscure.
- To darken.
- To confuse: his emotions obfuscated his judgment.
[LLat. obfuscare, to darken : ob(intensive) + Lat. fuscare,
to darken < fuscus, dark.] -obfuscation n. obfuscatory adj
- The IOCCC:
- To write the most Obscure/Obfuscated C program within the rules.
- To show the importance of programming style, in an ironic way.
- To stress C compilers with unusual code.
- To illustrate some of the subtleties of the C language.
- To provide a safe forum for poor C code. :-)
Be sure to also to look at the IOCCC twitter feed.
Source code has been released for version 0.24 2022-01-15 of the
a tool that is based on, and is containing, the official iocccsize tool,
will form a compressed tarball that a registered IOCCC contestant
will upload to the submit server (when the contest is open of course).
The mkiocccentry tool and the iocccsize tool
are in alpha test at the moment and is subject to change before IOCCC28 opens.
Comments, suggestions, compile warnings/errors, fixes, and typo corrections to
the mkiocccentry tool are welcome via a
GitHub pull request
or by filing a
or by sending
Email to the IOCCC judges.
are re-tooling how we run the IOCCC.
Our goal is to build a smoother, more rapid process centered around
For example, when we announce the winners,
we will do so by committing their code to the
of the IOCCC repo, so that people will be able immediately
view the winning source.
We plan to refactor and modernize the IOCCC web site.
We also plan to build a new and improved way to submit entries the next IOCCC.
As a result of all this work we need to do,
we plan to hold IOCCC28 in 2022 instead of 2021.
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
Stay tuned for how you may be able to help in the IOCCC redesign for IOCCC28!
- Email to IOCCC, via this email address:
with the following two words (separated by a space) somewhere in the subject of your email:
We apologize for the Email outage of the past few days.
- A temporary side effect of our move to using
Email to/from *@ioccc.org has been disabled.
We expect restore Email service in a few days.
When we do, we will announce restoration of Email service here.
- We sure to use URLs of the form https://www.ioccc.org/* that
include the www. when accessing the
IOCCC web site.
- Due to current world events, we are extending the 27th IOCCC until 2020-May-15 06:26:49 UTC
- The submission tool will now be active until 2020-May-15 06:26:49 UTC
- The source code for the winners of the 26th IOCCC has been released.
- The 27th IOCCC will be open from 2019-Dec-26 06:01:41 UTC (Boxing Day)
to 2020-Mar-15 06:26:49 UTC (Ides of March).
- The submission tool will be available around 2020-Jan-15 15:15:15 UTC.
- Draft Rules, Guidelines and IOCCC size tool for the 27th IOCCC are available.
- Due to some delays, we now plan to publish source and annotations in early July 2019.
Older news has been archived, but is not currently available