Compiler splitted into two parts * A compiler frontend - the one that compiles bytecode (Smalltalk or Java or ...) into lower-level instructions using backend * A compiler backend that provides / will provide low-level API for frontend, hiding all the details of architecture differences and LLVM interfacing.

C1: Fixed context setup for non-tradstack machines (such as x86_64)

Fixed typo in VMConstants (concatenated pool variable names)

C1: Added C1CompilerDebugFlags pool with (for now few) debug flags These can be used by the compiler to produce detailed log and/or insert debug code to into generated code.

C1: Changed method naming convention All (helper) methods that generate code (LLVM IR) are either * "loadXYZ" for loading from memory into value, * "storeXYZ" for storing a value into memory * or "emitXYZ" for all the rest of codegen helpers

C1: Added #emitReturn: helper

Initial support for message sends. For now, the C1 compiler uses simple `__SSENDx`s so no need to bother with inline caches. This can (and will) be addressed in a future.

Initial support for literals

Simple method prologue / epilogue implementation * prologue always allocate a new context and updates __thisContext register. * epilogue always fetches return value from retvalTemp and calls __MKREALCONTEXT5() This should do for now, even though this is not always the most effective way of doing things.

Merge