AK
«Ужасы нашего городка» :)
Отсюда: http://blog.erlang.org/the-road-to-the-jit/
BEAM/C generated a single C function for each Erlang module. Local calls within the module were made by explicitly pushing the return address to the Erlang stack followed by a goto to the label of the called function. (Strictly speaking, the calling function stores the return address to BEAM register and the called function pushes that register to the stack.)
Calls to other modules were done similarly by using the GCC extension that makes it possible to take the address of a label and later jumping to it. Thus an external call was made by pushing the return address to the stack followed by a goto to the address of a label in another C function.Отсюда: http://blog.erlang.org/the-road-to-the-jit/
Просто вместо генерации машинного кода напрямую использовали чуть более высокоуровневое представление в виде си, с теми же подходами :)
