I'm not sure of the underlying reason for the gcc benchmark anomaly (the clang numbers don't change). name old speed new speed delta wuffs_jpeg_decode_19k_8bpp/clang11 227MB/s ± 0% 227MB/s ± 0% ~ (p=0.151 n=5+5) wuffs_jpeg_decode_30k_24bpp_progressive/clang11 209MB/s ± 0% 213MB/s ± 0% +1.62% (p=0.008 n=5+5) wuffs_jpeg_decode_30k_24bpp_sequential/clang11 379MB/s ± 0% 380MB/s ± 0% +0.13% (p=0.008 n=5+5) wuffs_jpeg_decode_77k_24bpp/clang11 329MB/s ± 0% 329MB/s ± 0% +0.06% (p=0.008 n=5+5) wuffs_jpeg_decode_552k_24bpp_420/clang11 342MB/s ± 0% 342MB/s ± 0% ~ (p=0.690 n=5+5) wuffs_jpeg_decode_552k_24bpp_444/clang11 468MB/s ± 0% 469MB/s ± 0% +0.10% (p=0.008 n=5+5) wuffs_jpeg_decode_4002k_24bpp/clang11 348MB/s ± 0% 348MB/s ± 0% +0.08% (p=0.016 n=5+5) wuffs_jpeg_decode_19k_8bpp/gcc10 213MB/s ± 0% 213MB/s ± 0% ~ (p=0.151 n=5+5) wuffs_jpeg_decode_30k_24bpp_progressive/gcc10 221MB/s ± 0% 246MB/s ± 0% +11.51% (p=0.008 n=5+5) wuffs_jpeg_decode_30k_24bpp_sequential/gcc10 487MB/s ± 0% 482MB/s ± 0% -0.98% (p=0.008 n=5+5) wuffs_jpeg_decode_77k_24bpp/gcc10 392MB/s ± 0% 392MB/s ± 0% ~ (p=1.000 n=5+5) wuffs_jpeg_decode_552k_24bpp_420/gcc10 413MB/s ± 0% 412MB/s ± 0% ~ (p=0.190 n=4+5) wuffs_jpeg_decode_552k_24bpp_444/gcc10 459MB/s ± 0% 460MB/s ± 0% +0.09% (p=0.008 n=5+5) wuffs_jpeg_decode_4002k_24bpp/gcc10 419MB/s ± 0% 419MB/s ± 0% +0.04% (p=0.008 n=5+5)
Releases (in the C Programming Language)
Wuffs the Library ships as a "single file C library", also known as a "header file library".
To use that library in your C/C++ project, you just need to copy one file from
this directory, or otherwise integrate that one file into your build system.
Typically, pick the latest stable version (but not the unsupported snapshot),
with a filename like wuffs-vMAJOR.MINOR.c for version MAJOR.MINOR.
To use that single file as a "foo.c"-like implementation, instead of a
"foo.h"-like header, #define WUFFS_IMPLEMENTATION before #include'ing or
compiling it.
Latest Stable Version
Version 0.2 (December 2019) is the latest stable version. Stable means that its API won't change any further, but being a "version 0.x" means that:
- It will not have long term support.
- Newer versions make no promises about compatibility.
Mirror
Wuffs' canonical repository is located at
github.com/google/wuffs. If you just want to
use Wuffs-the-library in its C form (instead of modifying its Wuffs form or
otherwise needing Wuffs-the-language tools), a mirror of just the release/c
directory is located at
github.com/google/wuffs-mirror-release-c.
By excluding everything else, the mirror is much smaller than and changes much
less frequently than the canonical repository.