The meaning of "obfuscated C" as the contest requires was not well-defined at that time and had to be amended for a very long time. There are at least 5 more entries that abused and subsequently changed the rules at that time [1] [2] [3] [4] [5]. ([6] is an exception; this kind of abuse of the rules is allowed and now common.)
> [...] if compilers started doing funny things with it, you wouldn't be able to write things like JITs at all.
Well, see [7].
[1] https://www.ioccc.org/1987/biggar/hint.html
[2] https://www.ioccc.org/1988/spinellis.hint
[3] https://www.ioccc.org/1989/jar.1.hint
[4] https://www.ioccc.org/1993/lmfjyh.hint
[5] https://www.ioccc.org/1994/smr.hint
As it stands, it's very interesting to read but most examples are hard to run and I always end up going away unfulfilled.
Works on x86/x86_64 Linux:
char main[] __attribute__ ((section(".text"))) = "\xe8\x0d\0\0\0Hello world!\n"
#ifdef __x86_64__
"\x31\xc0\x8d\x50\x0d\xff\xc0\x89\xc7\x5e\x0f\x05\x31\xff\x8d\x47\x3c\x0f\x05";
#else
"\x31\xdb\x8d\x53\x0d\x59\x8d\x43\x04\x43\xcd\x80\x31\xdb\x8d\x43\x01\xcd\x80";
#endif