Right, JIT compilers in Common Lisp are mostly not known. There are only a few bytecode interpreters, where it could be used: CLISP, CMU CL with its bytecode in

Right, JIT compilers in Common Lisp are mostly not known. There are only a few bytecode interpreters, where it could be used: CLISP, CMU CL with its bytecode interpreter, ... Common Lisp has several execution modes and for compiled code: important are 1) AOT compiled, but fully safe with optional debug info: safety = 3 and debug = 2 2) AOT compiled, but fast and potentially unsafe with little debug infos: speed = 3, safety = 0, debug = 0 The usual goal is to be able to run much of the code in mode 1) and only compile portions in mode 2). Thus much of the language is optimized around possible compilation. The language is very dynamic, but there is also a core, which is not object-oriented - thus potentially easier to compile to fast code. Also incremental in-memory compilation in Common Lisp is AOT and not JIT.