Once a day, we take patches from our bleeding-edge source repository – next, run our testsuite and if everything works out, we make those patches available in our current repository (see also downloads). In other words, the current repository is expected to be in a useable state at all times. The code in current is then subject to additional testing and if the results are satisfactory, a release tarball is made.

Latest Changes

Test Results

summary: 2 failed, 99 skipped, 662 passed

abstract
bricks
c
cc
cpp
demo
dios
lart
libc
libcxx
pdclib
posix
pthread
pts
sim
undef
verify
vm
weakmem