Files
ioccc/2011
Landon Curt Noll 21c3e89a2f improve tarballs
The `make quick_www` and `make www` rules in the top level `Makefile`
no longer build compressed tarballs.

The tools that form compressed tarballs now add _--no-xattrs --no-selinux_
when building compressed tarballs.

Changed `bin/tar-all.sh` VERSION from "1.0.1 2024-02-23"
to "1.1 2024-02-27".

Changed `bin/tar-entry.sh` VERSION from "1.0.1 2024-02-23"
to "1.1 2024-02-27".

Changed `bin/tar-year.sh` VERSION from "1.0.1 2024-02-23"
to "1.1 2024-02-27".

Added `make tar` rule to the top level `Makefile` to create all
compressed tarballs.  In particular `make tar` calls:

* make clobber
* make genpath
* make genfilelist
* make verify_entry_files
* make form_entry_tarball
* make form_year_tarball
* make form_all_tarball

Performed `make tar` in an effort to see of tar warnings such as
have been fixed:

```
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.quarantine'
```

**NOTE**: We to **NOT** plan to rebuild compressed tarballs while some of the
((**top priority**)) issues are active.  We only rebuilt the compressed tarballs
as a test.
2024-02-27 23:21:32 -08:00
..
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-27 23:21:32 -08:00
2024-02-17 22:49:28 -08:00
2024-02-27 23:21:32 -08:00
2023-10-07 04:35:47 -07:00

Twentieth International Obfuscated C Code Contest

Standard IOCCC stuff

Look at the README.md file for the given winning entry for information on how to compile it 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.

The IOCCC has a web site and now has a number of international mirrors. The primary site can be found at,

https://www.ioccc.org/

Use make to compile entries. It is possible that on non-Unix / non-Linux systems the Makefile needs to be changed. See the Makefile for details.

This year we included most of the information included by the submitters in the README.md files.

Read over the Makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define).

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.

Remarks on some of the entries

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

  • did not follow the "one program - one file" rule;

  • depended too much on 32 bit architectures;

  • were more of the "obfuscated math" kind rather than the "obfuscated C" kind.

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

We believe you will be impressed with this year's winners. The Best of Show is a fine example of character stitching. But don't ignore the other winners! There are games, puzzle solvers, utilities, eye candy, calculators and graphical and audio tools.

This year all winners are different, and there is a winner from a new country - China! Many winners won for the first time. (Please note that judging is done completely anonymously. Be warned that we may disqualify entries that reveal the identity of the submitter).

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 addition information on the IOCCC.

Copyright and License

Copyright (c) 2012,2023, Landon Curt Noll and Leonid A. Broukhis. All Rights Reserved. This work is licensed under a Creative Commons CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International license. If you do use this work in some form, the IOCCC judges would appreciate (but does not require) if you were to send us a note about your use.