Slashdot Mirror

← Back to Stories (view on slashdot.org)

Source Code For 22nd IOCCC Winners Has Been Released

Posted by Soulskill on from the go-small-or-go-home dept.

An anonymous reader writes "The source code for the 22nd International Obfuscated C Code Contest winners has finally been released. Many entries exploited bugs in the size check program, making the 2013 entries possibly the most featureful submissions ever."

14 of 47 comments (clear)

  1. Perl by Threni · · Score: 5, Funny

    Is there one for Perl, but the other way around - where it's clear what the code is actually doing?

  2. It's not just the obfuscation... by LikwidCirkel · · Score: 4, Interesting

    I find this very impressive, not so much for the obfuscation, but for packing so much functionality into a small bit of code....

    http://ioccc.org/2013/cable3/hint.html

    1. Re:It's not just the obfuscation... by hydrofix · · Score: 2

      There might be more to that entry than meets the eye. Quoting its description:

      CPU supports the full 8086/186 instruction set. Due to the complexities of the 8086’s arbitrary-length instruction decoding and flags, 8086 instructions are first converted to a simpler intermediate format before being executed. This conversion, along with instruction lengths and how each instruction modifies the flags, is assisted by some lookup tables which form part of the BIOS binary.

      The BIOS binary is over 12 kilobytes, so it raises the question as to which extent the emulation might be actually achieved by the BIOS.

    2. Re:It's not just the obfuscation... by icebike · · Score: 2

      I'm just glad the published these guys names.
      Every HR department now will know never to hire them for work on any production code.

      --
      Sig Battery depleted. Reverting to safe mode.
    3. Re:It's not just the obfuscation... by rusty0101 · · Score: 2

      Actually, the reverse is mostly true.

      Most companies want to be able to find developers who can do this, as it means that they have someone on staff (or available) who will go to the trouble of figuring out just what it is that the spagetti code that did make it to production actually does. Someone who can write this level of code, can often get the company in question out of trouble that even the original developer could not, or perhaps would charge excessively high "support" fees based on the perception that they are the only ones capable of reading the code they produced to begin with.

      That said, someone who can do this can probably put in all kinds of back door's to programs, but that's what you implement a code audit and QA department for.

      --
      You never know...
  3. For example... by bhlowe · · Score: 3, Insightful

    char*_ = "'""/*"; #include #define m 21 #define o(l, k) for(l=0; lGP9$5-,#C?NX"]-35)>>t*3 o(e,4){ c[T] [e][t]=("5'##>4(" [T+t+T]-35)>>e*2 } } n(15) { s=T>9?m:(T&3)-3?15:36;o(e,s)o(t,2)c[T+19][e][t]="6*6,8*6.608.6264826668\ 865::(+;0(6+6-6/8,61638065678469.;88))()3(6,8*6.608.6264826668865:+;4)-*6-6/616365,\ -6715690.5;,89,81+,(023096/:40(8-7751)2)65;695(855(+*8)+;4**+4(((6.608.626482666886\ 5:+;4+4)0(8)6/61638065678469.;88)-4,4*8+4(((60(/6264826668865:+;4-616365676993-9:54\ +-14).;./347.+18*):1;-*0-975/)936.+:4*,80987(887(0(*)4.*""/4,4*8+4(((6264826668865:\ +;4/4-4+8-4)0(8)6365678469.;88)1/(6*6,6.60626466686:8)8-8*818.8582/9863(+;/""*6,6.6\ 0626466686:4(8)8-8*818.8582/9863(+;/,6.60626466686:8-818.8582/9864*4+4(0())+;/.6062\ 6466686:8/8380/7844,4-4*4+4(0())69+;/0626466686:818582/9864.4/4,4-4*4+4(0())+;" [e+E +e+t]-40; E+=s+s; } n(45){ if(T>i) { v(2,T,7); v(46,T,7); } v(2+T,44,7); } T=0; o(e, 42)o(t,m)h[T][e][t]--; while(R+i) { s = D=0; if (r-R) { n(19) if (G[R+i][T]+i) V=T/2 ; else if(G[R][T]+i) s++; if(s) { if(V>4){ V=9-V; D++; } V+=29; n(20) q(c[V][T][0],c [V][T][i],D); } } n(19) if((L=G[R][T])+i) { O=T-L; e=O>9; t=e?18-O :O; o(K,((t&3)-3? 16:37)){ if(K){ L=c[t+19][K-i][0]; O=c[t+19][K-i][i] ; } q(L,O,K && e); } } if(s) q( c[V][20][0], c[V][20][i], D); R--; } printf("\33[47;1f\33[?25h\33[40m"); return 0; } // TODO: Add comments.

    1. Re:For example... by davester666 · · Score: 5, Funny

      looks like it'll work. ship it. we'll fix any problems in v2.

      --
      Sleep your way to a whiter smile...date a dentist!
  4. It's amazing that they don't link to the source co by Anonymous Coward · · Score: 5, Insightful

    For a contest involving writing source code, it's astounding and infuriating that the judges did not link to the source code in the results.

  5. Ray tracer + web server + image encoder + clock by hydrofix · · Score: 5, Interesting

    I found this one a pretty mind-blowing entry. When compiled and run, it creates a web server at http://localhost:8224, which can be opened in a browser to display a ray-traced 3D scene of steel ball bearings on a checker-pattern surface, arranged to display the current time. Quoting the description:

    The program wears many hats (not literally). It is
    * a web server
    * a PNG encoder
    * a ray tracer
    * a clock

    Unlike the PC emulator entry, it does not require a binary blob and all the code and data fit within the 4 kilobyte limit.

    1. Re:Ray tracer + web server + image encoder + clock by hydrofix · · Score: 2

      Does the program include its own PNG format algorithms, or am I missing something?

      Same goes for the web server: did he really write his own web server in mills.c?

      Well in a way, yes for both. He only uses standard C libraries, so there is indeed no PNG library or an HTTP server #included. But due to the size limitations, the code can probably only produce one exact type of PNG image and the HTTP server can only serve one page, so those are not "proper" implementations by any means. For example, the HTTP server ignores the request path and the result of accessing http://localhost:8224/ http://localhost:8224/foo and http://localhost:8224/foo/bar is alwyas the same – pretty useless for a "real" HTTP server. If you look up the .C file, it's typeset in an artistic manner, resembling one of the ball bearings in the rendered end result. So, the point, like with many other IOCCC entries, is to demonstrate how some seemingly very complex tasks can be achieved by short, obfuscated C files.

    2. Re:Ray tracer + web server + image encoder + clock by Anonymous Coward · · Score: 2, Insightful

      in the demoscene, which is unfortunately dead

      Uh, no it's not?

  6. Largest small system emulator - Humbling by Flammon · · Score: 2

    Humbled after reading Largest small system emulator. http://ioccc.org/2013/cable3/hint.html

    --
    ayottesoftware.com
  7. Re:It's amazing that they don't link to the source by Art+Challenor · · Score: 4, Funny

    For a contest involving writing source code, it's astounding and infuriating that the judges did not link to the source code in the results.

    What did you expect? It's a contest for writing obfuscated code and you expect a webpage that has clear, concise information?

  8. Busted! by Trax3001BBS · · Score: 2

    "As I was writing up this description, I discovered I'm not the first person to write an obfuscated C sparkline utility! Vicent Martí created
    [this one](https://gist.github.com/vmg/1368661) years (!) ago. (My implementation is completely independent.)" http://ioccc.org/2013/dlowe/hint.text

    I fully believe this was a coincidence, but one can never say they hadn't seen it or similar before as it's would appear within their circle of interest.

    But to complete this project then find an older version must be deflating in some manner.