llvm-project/llvm/tools/llee/README.txt

              LLEE: (LL)VM (E)xecution (E)nvironment

This tool presents a virtual execution environment for LLVM programs. By
preloading a shared object which defines a custom execve() functions, we can
execute bytecode files with the JIT directly, without the user ever thinking
about it.

Thus, a user can freely run any program, native or LLVM bytecode, transparently,
and without even being aware of it.

To use LLEE, run `./llee <native_program>', a good choice is a shell. Anything
started within that program will be affected by the execve() replacement.
A lot of changes were suggested by Chris. ExecveHandler.c: * Use "" instead of <> for LLVM include files * Use raw I/O, we don't need buffering * Set errno = 0 before using open() * strlen() doesn't count NULL terminator in its size * Use memcmp() instead of strcmp() * Return result of the real execve(), not 0 * Search for path to bytecode file if not absolute/relative path SysUtils.c: * Convert all comments to C-style * Stop using `bool', use `unsigned' instead SysUtils.h: * Stop using `bool', use `unsigned' instead * Updated comment to FindExecutable() README.txt: * Describe the goal of LLEE and an application llvm-svn: 7911 2003-08-16 07:31:16 +08:00			`LLEE: (LL)VM (E)xecution (E)nvironment`

			`This tool presents a virtual execution environment for LLVM programs. By`
			`preloading a shared object which defines a custom execve() functions, we can`
			`execute bytecode files with the JIT directly, without the user ever thinking`
			`about it.`

			`Thus, a user can freely run any program, native or LLVM bytecode, transparently,`
			`and without even being aware of it.`

			To use LLEE, run `./llee <native_program>', a good choice is a shell. Anything
			`started within that program will be affected by the execve() replacement.`