mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Attempt to fix conflicts

Browse Source 
As some commits from yesterday and this morning caused conflicts with
commits I made last week I'm trying to fix it on the branch that I
believe introduced the changes. If this does not work I do not know what
I'll do but it have to be done another time.
This commit is contained in:
Cody Boone Ferguson committed 2023-02-22 07:29:22 -08:00
1 parent aac3522e25
commit 0e9136f9fb
27 files changed
+325 -278
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1984/README.md
+8
View File
@@ -1,10 +1,18 @@
In 1984, the first contest was held. The name of the contest was simply
``Obfuscated C Code Contest''.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Restrictions against machine dependent code were not in the rules in 1984.
The source file size restriction was only 512 bytes. Rules and results
were posted to net.lang.c and net.unix-wizards.
=-=
Copyright (c) 1984, Landon Curt Noll.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
1985/README.md
+9 -1
View File
@@ -1,4 +1,10 @@
185 marked the second year of the Obfuscated C Code Contest.
1985 marked the second year of the Obfuscated C Code Contest.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Hints against machine dependent code were added to the rules to avoid
another 1984 style winner. Rules and results were posted to net.lang.c
@@ -6,6 +12,8 @@ and net.unix-wizards. Larry Bassel was invited to help in the
judging. Awards were given to 5 classes of programs since we were
unable to select only the best 4.
=-=
Copyright (c) 1985, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
1986/README.md
+13 -5
View File
@@ -1,10 +1,10 @@
The 1986 contest was named: "The Third International Obfuscated C Code Contest"
Copyright (c) 1986, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The rules for 1986 suggested categories due to the success of the 1985
judging method. The maximum size was increased from 512 to 1024 bytes.
@@ -18,3 +18,11 @@ Rules and results were posted to net.lang.c and net.unix-wizards.
Micro/Systems Journal published started regular publishing of the winners.
The practice of making first announcement of the winners at the Summer
Usenix BOF started this year. A notice was posted to net.announce.
=-=
Copyright (c) 1986, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1987/README.md
+13 -5
View File
@@ -1,10 +1,10 @@
1987 marked the "The Fourth International Obfuscated C Code Contest"
Copyright (c) 1987, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The rules for 1987 suggested even more categories than in 1986. Hints
for what to do and not to do were also given in the rules. For
@@ -19,3 +19,11 @@ published the 1987 winners. Mark Horton included a version of the 1987
winners in an appendix of his C book. The first announcement of
winners at the Summer 87 Usenix was helped by a small fly that
danced all over the foils.
=-=
Copyright (c) 1987, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1988/README.md
+13 -5
View File
@@ -1,10 +1,10 @@
1988 marked the "The Fifth International Obfuscated C Code Contest"
Copyright (c) 1988, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The maximum size of entries was raised from 1024 to 1536 bytes, however
smaller entries were encouraged. Due to the "Best Abuse of the Rules"
@@ -21,3 +21,11 @@ Winning entries for previous years were repackaged with each year
being in its own directory. Make files and hints were also provided.
The package was posted to the: comp.sources.unix newsgroup. They are
also available on a wide number of Usenet archive sites.
=-=
Copyright (c) 1988, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1989/README.md
+15 -10
View File
@@ -1,16 +1,14 @@
1989 marked the "The Sixth International Obfuscated C Code Contest"
Copyright (c) 1989, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Instructions for use: Run make to compile entries (it is possible
that on System V or non-unix systems the makefile needs to be
changed). Look at the source and try to figure out what the programs
do, and run them with various inputs. If you want to, look at the
hints files for (minor) spoilers.
changed).
This year, the Grand Prize was given to the most useful program.
@@ -18,8 +16,7 @@ The "Strangest abuse of the rules" award was given this year to stress
the fact that starting in 1990, compiling entries must result an
executable regular file.
In two other cases, we included System V portable versions of winning
programs. The makefile always uses the portable version of the "Best
The makefile always uses the portable version of the "Best
self modifying program" because there as no loss of functionality in
using it. In the case of the "Best game" winner, however, some
functionality is lost in the portable version and so the makefile uses
@@ -30,3 +27,11 @@ Rules and results were posted to comp.lang.c, comp.sources.unix, and
alt.sources. They have been made available on a wide number of Usenet
archive sites such as uunet. The 1989 winners will be published in the
Micro/Systems Journal.
=-=
Copyright (c) 1989, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1990/README.md
+12 -12
View File
@@ -1,18 +1,10 @@
1990 marked the "The Seventh International Obfuscated C Code Contest"
Copyright (c) 1990, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Instructions for use: Run make to compile entries (it is possible that
on System V or non-unix systems the makefile needs to be changed). The
ansi.mk may need to be changed if your ANSI C compiler is not gcc.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
(minor) spoilers.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
This year, the Grand Prize won a standing ovation at USENIX.
@@ -31,3 +23,11 @@ some of the contest entries were appreciated.
Rules and results were posted to comp.lang.c, comp.sources.unix, and
alt.sources. They have been made available on a wide number of Usenet
archive sites such as uunet.
=-=
Copyright (c) 1990, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1991/README.md
+13 -9
View File
@@ -1,18 +1,14 @@
1991 marked the "The Eighth International Obfuscated C Code Contest"
Copyright (c) 1991, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Instructions for use: Run make to compile entries. It is possible that
on BSD or non-unix systems the makefile needs to be changed.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
(minor) spoilers.
This year, we did not single out an entry that was better than all of
the rest. We selected 3 entries that were, in our opinion, went beyond
all of the other entries this year:
@@ -86,3 +82,11 @@ Credits:
We would like to thank Barbara Frezza for her role as official chef
of the contest. Landon Noll appreciated the opportunity to serve
as assistant pizza chef. Larry Bassel was official taste tester. Yummo!
=-=
Copyright (c) 1991, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1991/ant/README.md
+8 -17
View File
@@ -1,4 +1,4 @@
## Best Utility:
# Best Utility:
Anthony C Howe
Mortice Kern Systems Inc. #CL-23
@@ -7,34 +7,25 @@
Canada, N2J 2W9 Canada, N2L 6G9
## Judges' comments:
## To build:
Make and run with a filename (writable or to be created) as an argument.
For example, try:
make all
### To run
make ant
cp ant.hint hill
./ant hill
Note that some old BSD systems may have trouble compiling this entry.
They may complain about 'idlok' being undefined. You can fix this
by changing line 26 from:
2;initscr();d=LINES;raw();noecho();idlok(stdscr,1);if(0<(i= ...
to:
2;initscr();d=LINES;raw();noecho();if(0<(i= ...
## Judges' comments
***or*** update to a modern version of Un*x. :-) If you have source,
you can use this entry to help in your upgrade.
You may need to change the makefile depending on what type of system
you are running. See the notes in ansi.mk or common.mk.
The author was kind enough to supply a list of references below,
in case you are still confused after read the source! :-)
## Author's comments
## Selected notes from the author:
Ant's Editor vIOCCC91
1992/README.md
+13 -10
View File
@@ -1,19 +1,14 @@
1992 marked the "The Ninth International Obfuscated C Code Contest"
Copyright (c) 1992, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define). A number of compilers had problems optimizing certain
@@ -86,3 +81,11 @@ Credits:
We would like to thank Barbara Frezza for her role as official chef of
the contest. Landon Noll and Larry Bassel appreciated the opportunity
to serve as official taste testers. Yummo!
=-=
Copyright (c) 1992, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1992/ant/README.md
+14 -7
View File
@@ -1,4 +1,4 @@
Best Utility:
# Best Utility:
Anthony C Howe
Mortice Kern Systems Inc.
@@ -7,14 +7,21 @@ Best Utility:
N2J 3G4
Canada
## To build:
Judges' comments:
To use:
make all
### To run
make am
./am ant.test.mk
## Judges' comments
Like much of Posix, obfuscation has its place. Your task is to
figure out where.
@@ -23,12 +30,12 @@ Judges' comments:
P1003 sub-committee.
We also suggest that you try:
make am
./am Makefile am_clobber <-- clobber everything except am
./am Makefile am_clobber # clobber everything except am
./am Makefile all
Selected notes from the author:
## Author's comments
See the file ant.README.
1993/README.md
+13 -10
View File
@@ -1,19 +1,14 @@
1993 marked the "The Tenth International Obfuscated C Code Contest"
Copyright (c) 1993, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -57,3 +52,11 @@ Credits:
We would like to thank Barbara Frezza for her role as official chef
of the contest. Landon Noll and Larry Bassel appreciated the opportunity
to serve as official taste testers. And as usual, the food was excellent.
=-=
Copyright (c) 1993, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1994/README.md
+12 -10
View File
@@ -1,20 +1,14 @@
1994 marked the "The Eleventh International Obfuscated C Code Contest"
Copyright (c) 1994, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -136,3 +130,11 @@ Pasta: Linguine with wild mushrooms and Reggiano Parmesan
Seafood: Salmon in cream sauce or lobster claws
Vegetable: Zucchini
Dessert: Homemade chocolate/pecan brownies, fruit
=-=
Copyright (c) 1994, Landon Curt Noll & Larry Bassel.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from both Landon Curt Noll and Larry Bassel.
1995/README.md
+11 -10
View File
@@ -1,11 +1,10 @@
1995 marked the "The Twelfth International Obfuscated C Code Contest"
Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from Landon Curt Noll, Larry Bassel and Sriram Srinivasan.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The IOCCC has an official home page:
@@ -17,11 +16,6 @@ announcements and much more.
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -140,3 +134,10 @@ Main Course: Cracked dungeness crab with lemon mayonnaise, broccoli,
mixture of white and brown rice
Dessert: Key lime pie
=-=
Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from Landon Curt Noll, Larry Bassel and Sriram Srinivasan.
1996/README.md
+13 -11
View File
@@ -1,15 +1,14 @@
1996 marked the "The Thirteenth International Obfuscated C Code Contest"
Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from Landon Curt Noll and Sriram Srinivasan.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The IOCCC has an official home page:
http://www.ioccc.org
@@ -20,11 +19,6 @@ announcements and much more.
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -95,3 +89,11 @@ us a line. We enjoy seeing who, where and how the contest is used.
If you have problems with any of the entries, AND YOU HAVE A FIX, please
email the fix (patch file or the entire changed file) to the above address.
=-=
Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan.
All Rights Reserved. Permission for personal, educational or non-profit use is
granted provided this this copyright and notice are included in its entirety
and remains unaltered. All other uses must receive prior permission in writing
from Landon Curt Noll and Sriram Srinivasan.
1998/README.md
+14 -12
View File
@@ -1,16 +1,14 @@
1998 marked the "The Fourteenth International Obfuscated C Code Contest"
Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach
and Leonid A. Broukhis, 1999.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The IOCCC has its own domain. The IOCCC has an official home page is now:
http://www.ioccc.org
@@ -18,11 +16,6 @@ The IOCCC has its own domain. The IOCCC has an official home page is now:
Use make to compile entries. It is possible that on BSD or non-unix
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -131,3 +124,12 @@ The next IOCCC is planned to start towards the end of 1999. Watch:
http://www.ioccc.org
for news of the next contest.
=-=
Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach
and Leonid A. Broukhis, 1999.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
2000/README.md
+14 -13
View File
@@ -1,23 +1,16 @@
2000 marked the "The Fifteenth International Obfuscated C Code Contest"
Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis, 2000.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
Standard IOCCC stuff
--------------------
Use make to compile entries. It is possible that on non-Un*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
@@ -118,3 +111,11 @@ p.s. The has been mentioned in an Amici Curiae for the DeCSS case. See:
and seach on the word ioccc (twice).
=-=
Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis, 2000.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
2001/README.md
+13 -13
View File
@@ -1,29 +1,22 @@
2001 marked the "The Sixteenth International Obfuscated C Code Contest"
Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis, 2001-2002.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
http://www.ioccc.org
Use make to compile entries. It is possible that on non-Un*x / non-Linux
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -95,3 +88,10 @@ Watch:
for news of the next contest.
=-=
Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis, 2001-2002.
All Rights Reserved. Permission for personal, educational or non-profit
use is granted provided this copyright and notice are included in its
entirety and remains unaltered. All other uses must receive prior permission
from the contest judges.
2004/README.md
+14 -12
View File
@@ -1,28 +1,22 @@
2004 marked the "The Seventeenth International Obfuscated C Code Contest"
Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis. All Rights Reserved. Permission for personal,
educational or non-profit use is granted provided this copyright and
notice are included in its entirety and remains unaltered. All other
uses must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
http://www.ioccc.org/
Use make to compile entries. It is possible that on non-Un*x / non-Linux
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
Read over the makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
#define).
@@ -84,3 +78,11 @@ Watch:
http://www.ioccc.org/
for news of the next contest.
=-=
Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach
and Leonid A. Broukhis. All Rights Reserved. Permission for personal,
educational or non-profit use is granted provided this copyright and
notice are included in its entirety and remains unaltered. All other
uses must receive prior permission from the contest judges.
2005/README.md
+15 -11
View File
@@ -1,28 +1,25 @@
2005 marked the "The Eighteenth International Obfuscated C Code Contest"
========================================================================
Copyright (C) 2005, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
> <http://www.ioccc.org/>
Use make to compile entries. It is possible that on `non-Un*x` / non-Linux
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
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).
@@ -108,3 +105,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
=-=
Copyright (C) 2005, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2006/README.md
+15 -11
View File
@@ -1,28 +1,25 @@
2006 marked the "The Nineteenth International Obfuscated C Code Contest"
========================================================================
Copyright (C) 2006, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
> <http://www.ioccc.org/>
Use make to compile entries. It is possible that on non-Un*x / non-Linux
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
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).
@@ -79,3 +76,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
=-=
Copyright (C) 2006, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2011/README.md
+15 -11
View File
@@ -1,28 +1,25 @@
2011 marked the "The Twentieth International Obfuscated C Code Contest"
========================================================================
Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
> <http://www.ioccc.org/>
Use make to compile entries. It is possible that on non-Un*x / non-Linux
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitters.
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).
@@ -77,3 +74,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
=-=
Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2012/README.md
+11 -19
View File
@@ -1,16 +1,15 @@
2012 marked the "The Twenty First International Obfuscated C Code Contest"
========================================================================
Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
@@ -19,11 +18,6 @@ The primary site can be found at,
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitter.
Read over the makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a #define).
@@ -132,12 +126,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
=-=
--------------------------------------------------------------------------------
<!--
(c) Copyright 1984-2012, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
[judges]: http://www.ioccc.org/judges.html
[cc]: http://creativecommons.org/licenses/by-sa/3.0/
-->
Copyright (C) 2012, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2013/README.md
+11 -19
View File
@@ -1,16 +1,15 @@
2013 marked the "The Twenty Second International Obfuscated C Code Contest"
===========================================================================
Copyright (C) 2013, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments 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,
@@ -19,11 +18,6 @@ The primary site can be found at,
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitter.
Read over the makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a #define).
@@ -112,12 +106,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
=-=
--------------------------------------------------------------------------------
<!--
(c) Copyright 1984-2013, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
[judges]: http://www.ioccc.org/judges.html
[cc]: http://creativecommons.org/licenses/by-sa/3.0/
-->
Copyright (C) 2013, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2018/ferguson/.gitignore
+1
View File
@@ -2,3 +2,4 @@ prog-simple
prog.orig
weasel
weasel-simple
prog
2019/README.md
+11 -18
View File
@@ -1,16 +1,15 @@
2016 marked the "The Twenty Sixth International Obfuscated C Code Contest"
==========================================================================
Copyright (C) 2019, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
Standard IOCCC stuff
--------------------
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The primary IOCCC web site can be found at,
> <http://www.ioccc.org/>
@@ -18,11 +17,6 @@ The primary IOCCC web site can be found at,
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitter.
Read over the makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a #define).
@@ -99,11 +93,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
--------------------------------------------------------------------------------
<!--
(c) Copyright 1984-2019, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
=-=
[judges]: http://www.ioccc.org/judges.html
[cc]: http://creativecommons.org/licenses/by-sa/3.0/
-->
Copyright (C) 2019, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
2020/README.md
+11 -17
View File
@@ -1,14 +1,13 @@
## 2020 marked the "The Twenty Seventh International Obfuscated C Code Contest"
Copyright (C) 2020, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.
## Standard IOCCC stuff
Look at the README.md file for the given winner for information
on how to compile the winner 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 comments for even more details.
The primary IOCCC web site can be found at,
> <http://www.ioccc.org/>
@@ -16,11 +15,6 @@ The primary IOCCC web site can be found at,
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
systems the makefile needs to be changed. See the Makefile for details.
Look at the source and try to figure out what the programs do, and run
them with various inputs. If you want to, look at the hints files for
spoilers - this year we included most of the information included
by the submitter.
Read over the makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a #define).
@@ -88,10 +82,10 @@ For news of the next contest watch:
> <http://www.ioccc.org/>
-----------------------------------------------------------------------------------------------------
(c) Copyright 1984-2020, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved
This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc].
=-=
[judges]: http://www.ioccc.org/judges.html
[cc]: http://creativecommons.org/licenses/by-sa/3.0/
-----------------------------------------------------------------------------------------------------
Copyright (C) 2020, Landon Curt Noll, Simon Cooper, and Leonid A.
Broukhis. All Rights Reserved. Permission for personal, educational
or non-profit use is granted provided this copyright and notice are
included in its entirety and remains unaltered. All other uses
must receive prior permission from the contest judges.