This actually puts out a mildly confusing picture. Rubinius uses LLVM to implement the JIT compiler only. LLVM does not provide a performant interpreter, and ev

This actually puts out a mildly confusing picture. Rubinius uses LLVM to implement the JIT compiler only. LLVM does not provide a performant interpreter, and even if it did, the instructions in LLVM are incredibly lowlevel which would mean even lower performance. For this reason, Rubinius also has a bytecode interpreter, of which the bytecodes are highlevel and associated directly with ruby semantics (send, push_const, etc).