Bayle Shanks's website: proj-plbook-plPartImplementationTools

Table of Contents for Programming Languages: a survey

LLVM

See LLVM

PyPy

See PyPy

JVM

See JVM

CLR

See CLR

Other runtimes and runtime libraries

Apache Portable Runtime

"OS threads, blocking IO, and other system things"

libuv

asynchronous I/O and some other stuff.

Used by nodejs, Rust language, Luvit, Julia, pyuv, MoarVM?.

libumem

Used by nodejs

helps with debugging memory leaks (see http://www.joyent.com/blog/walmart-node-js-memory-leak for an example)

Other useful runtime libraries

https://en.wikipedia.org/wiki/GNU_C_Library
- also Bionic, a simplified libc variant for Android
libuv for async I/O
libtommath for multiple precision arithmetic
uthash for hashes
libjit (see also http://codingrelic.geekhold.com/2010/07/exploring-libjit.html )

libatomic_ops

"Provides implementations for atomic memory update operations on a number of architectures"

"Note that experience with this package contributed to the design of C11 and C++11 atomics, which represent a careful refinement of the API. If your platform supports well-implemented C11 or C++11 atomics, please use those instead. "

documentation: http://en.cppreference.com/w/c/atomic

C11 atomics:

atomic_flag_test_and_set: sets an atomic_flag to true and returns the old value
atomic_flag_clear: sets an atomic_flag to false
atomic_store: stores a value in an atomic object
atomic_load: reads a value from an atomic object
atomic_exchange: swaps a value with the value of an atomic object
atomic_compare_exchange_strong: swaps a value with the an atomic object if the old value is what is expected, otherwise reads the old value
atomic_compare_exchange_weak: swaps a value with the an atomic object if the old value is what is expected, otherwise reads the old value (is like strong but allowed to fail spuriously)
atomic_fetch_add
atomic_fetch_sub
atomic_fetch_or
atomic_fetch_xor
atomic_fetch_and

All of the above atomics take an optional parameter, memory_order, which can be one of relaxed memory_order_relaxed, memory_order_consume, memory_order_acquire, memory_order_release, memory_order_acq_rel, memory_order_seq_cst. The default is memory_order_seq_cst (the strongest sequencing condition). Here's what these do: http://en.cppreference.com/w/c/atomic/memory_order

atomic_init: initializes an existing atomic object
atomic_is_lock_free: indicates whether the atomic object is lock-free
atomic_thread_fence: generic memory order-dependent fence synchronization primitive
atomic_signal_fence: fence between a thread and a signal handler executed in the same thread
atomic_flag (type; must be initialized with ATOMIC_FLAG_INIT). atomic_flag is lock-free. The other atomics may or may not be implemented with locks.
ATOMIC_VAR_INIT (note: this initialization operation is NOT atomic)

"Members of an atomic struct/union may not be accessed individually. The whole struct must first be copied to a non-atomic variable of compatible type."

"The ++,--, and compound assignment operators (e.g. +=) are atomic read-modify-write operations."

-- http://fileadmin.cs.lth.se/cs/Education/EDAN25/F06.pdf

proj-plbook-plPartImplementationTools