Coco needs some machine-specific features which are inherently non-portable. Although the coverage is pretty good, this means that Coco will probably never be a standard part of the Lua core (which is pure ANSI C).

Context Switching Methods

Coco relies on four different machine-specific methods for allocating a C stack and switching context. The appropriate method is automatically selected at compile time.

GCC Inline Assembler

This method is only available when GCC 3.x/4.x is used to compile the source. This is the fastest method for context switching, but only available for a few CPUs (see below).

Modified setjmp Buffer

This method changes a few fields in the setjmp buffer to redirect the next longjmp to a new function with a new stack frame. It needs a bit of guesswork and lots of #ifdef's to handle the supported CPU/OS combinations, but this is quite manageable.

This is the fallback method if inline assembler is not available. It's pretty fast because it doesn't have to save or restore signals (which is slow and generally undesirable for Lua coroutines).

POSIX ucontext

The POSIX calls getcontext, makecontext and switchcontext are used to set up and switch between different C stacks. Although highly portable and even available for some esoteric platforms, it's slower than the setjmp method because it saves and restores signals, too (using at least one syscall for each context switch).

You can force the use of ucontext (instead of setjmp) by enabling -DCOCO_USE_UCONTEXT in src/Makefile.

Windows Fibers

This is the standard method to set up and switch between different C stacks on Windows. It's available on Windows 98 and later.

None of the other methods work for Windows because OS specific code is required to switch exception handling contexts.

Supported Platforms

Coco has support for the following platforms:

CPU System Method
x86(any OS)gccasm
x64(any OS)gccasm
MIPS32(any OS)gccasm
ARM(any OS)gccasm
ARM64(any OS)gccasm
Sparc(any OS)gccasm
(any CPU)POSIXucontext
(any CPU)Windowsfibers

It should work pretty much anywhere where a correct POSIX ucontext implementation is available. It has been tested on every systems I could get hold of (e.g. Sparc, PPC32/PPC64, IA64, Alpha, HPPA with various operating systems).