Then compiled with Apple LLVM version 7.0.2 (clang-700.1.81) on OS X 10.11 (64-bit): clang bomb.c The total source size is 17+3 (for the -pg) = 20 bytes, which is easily within size limit. It doesn't even have to be able to start.Ĭompiled with Apple LLVM version 7.0.2 (clang-700.1.81) on OS X 10.11 (64-bit): clang bomb.c -o bomb -pg

What your program actually does is irrelevant, though it can't be anything malicious.It must compile without errors (warnings are OK), and crashing the compiler doesn't count for anything.available) compiler versions and operating systems (and obviously specify which you're using).

The environment is up to you, but in the interests of making this verifiable, please stick to recent (i.e.

Preprocessors are permitted only if they are a standard compilation option for your language.

if your compile line is gcc bomb.c -o bomb -O3 -lm, the -O3 -lm part (7 bytes) will be counted (note the initial leading space isn't counted). If you require specific flags when compiling, these count towards your byte limit (e.g.

It must be possible to invoke your compilation using a command or series of commands.

Specifically, no third party libraries or OS libraries. Static linking standard libraries is OK when it's supported.

You cannot use any other input than your source file(s) and the standard library of your language-of-choice.

Your source code can consist of multiple files, and even resource files, but the summed size of all these files must not exceed 512 bytes.

If your language-of-choice can't be compiled directly into one of those formats, transpilation followed by compilation is also allowed ( Update: you can transpile multiple times, just so long as you never use the same language more than once).

Net's CLR (other types of virtual bytecode are also likely to be OK if asked for).

The output of the compilation must be an ELF file, a Windows Portable Executable (.exe), or virtual bytecode for the JVM or.

OK, so there are a few important clarifications, definitions and restrictions Write some source code which occupies 512 bytes or less and which compiles into a file which occupies the most possible space. The challenge here is to abuse a compiler in the same way. Put simply, they are (relatively) small files which produce enormous output when interpreted by naïve software. You're probably familiar with zip bombs, XML bombs, etc.

Codeblocks compiler flags disappeared