ucontext implementation featuring glibc-compatible ABI
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ariadne Conill 33ff253d52 Merge pull request 'Fixed empty TYPE(__proc) causing linker issues on 32-bit arm' (#36) from rlcamp/libucontext:arm_linker_fix into master 6 months ago
arch Fixed empty TYPE(__proc) causing linker issues on 32-bit arm 6 months ago
doc add manual page 2 years ago
examples add cooperative threading example 2 years ago
include/libucontext include: missing stddef.h include for size_t 2 years ago
.gitignore test POSIX ABI compatibility in libucontext itself, too 2 years ago
.mailmap update copyright statements, add mailmap 3 years ago
.woodpecker.yml CI: also build armv7 10 months ago
LICENSE NEWS: prepare for 1.2 8 months ago
Makefile Added passthrough of FORCE_SOFT_FLOAT and FORCE_HARD_FLOAT Makefile options 7 months ago
NEWS NEWS: mention or1k port 7 months ago
README.md Added note to readme about floating point WIP 7 months ago
VERSION libucontext 1.2 7 months ago
libucontext.pc.in build: generate libucontext pkg-config file 2 years ago
libucontext_posix.c libucontext_posix: fix build under glibc 2 years ago
meson.build meson: Add option to pass cpu 1 year ago
meson_options.txt meson: Add option to pass cpu 1 year ago
test_libucontext.c test program: use libucontext-prefixed symbols 2 years ago
test_libucontext_posix.c add libucontext_posix test program 2 years ago



libucontext is a library which provides the ucontext.h C API. Unlike other implementations, it faithfully follows the kernel process ABI when doing context swaps.

Notably, when combined with gcompat, it provides a fully compatible implementation of the ucontext functions that are ABI compatible with glibc.

Since version 0.13, for some architectures, you can deploy to bare metal using newlib via the FREESTANDING=yes make option. Systems which use a syscall cannot work this way. The table below shows which architecture ports have been adapted to build with FREESTANDING=yes.

Adding support for new architectures is easy, but you need to know assembly language for the target to do it.

supported features

Architecture Works on musl Syscall Supports FREESTANDING Common trampoline


libucontext uses a simple makefile build system. You should define ARCH= at build time, otherwise the build system will attempt to guess using uname -m.

$ make ARCH=x86_64
$ make ARCH=x86_64 check
$ make ARCH=x86_64 DESTDIR=out install

There are a few options:

  • ARCH: The architecture libucontext is being built for. Must be set to one of the architectures listed in the feature support table. If unset, the build system will attempt to guess based on what architecture the host is running. Setting this option explicitly is highly recommended.

  • FREESTANDING: If this is set to yes, the system ucontext.h headers will not be used. Instead, the headers in arch/${ARCH}/freestanding will be used for definitions where appropriate. Default is no.

  • EXPORT_UNPREFIXED: If this is set to yes, the POSIX 2004 names getcontext, setcontext, swapcontext and makecontext will be provided as weak symbols aliased against their libucontext_ namespaced equivalents. This is necessary for libucontext to provide these functions on musl systems, but you may wish to disable this when using FREESTANDING mode to avoid conflicts with the target's libc. Default is yes.

  • DESTDIR: If this variable is set, the installed files will be installed to the specified path instead of the system root.

If you have scdoc installed, you can build manpages and install them:

$ make docs
$ make DESTDIR=out install_docs

real-world use cases

libucontext is used on almost all musl distributions to provide the legacy ucontext.h API. Additionally, it is used by:

  • UTM -- friendly qemu distribution for macOS and iOS devices. UTM uses libucontext as qemu's coroutine backend.

  • Lwan -- a high-performance embeddable asynchronous web server. Lwan uses libucontext to provide green threads when building on non-x86 architectures.


libucontext, while largely functionally equivalent does have some differences over traditional POSIX ucontext functions:

  • Saving and restoring the signal mask is not implemented by default in order to avoid kernel syscall overhead. Use -lucontext_posix if you actually need this functionality, which provides a POSIX compliant implementation at the cost of performance.

  • Only basic GPR registers are saved and restored when context swapping. The glibc implementation uses hardware capability detection to save/restore other register groups, such as the FPU registers or vector processing (AltiVec/AVX/NEON) registers. Adding this capability detection would significantly increase the complexity of the project and thus is not implemented. Support for compiling in code to save/restore FPU registers or vector registers may be added in a later release as a build-time setting -- for now, we assume a soft-float ABI with no optional processor features. In practice, this does not really matter, code using these functions are unlikely to be impacted by this design assumption. This is a work in progress, as newer compilers will spill even non-floating-point state through floating point registers when allowed to do so.