Files
wuffs/release/c
Nigel Tao 748e44fe71 base: skip bulk load/save on short slice length
This is about semantics (being easier to reason about if transforming
between u32 and u8 and the u8 slice length is short and not a multiple
of 4). It's not an optimization per se, but for the record, it does have
significant performance impact:

name                                             old speed      new speed      delta

wuffs_jpeg_decode_19k_8bpp/clang11                369MB/s ± 0%   376MB/s ± 0%   +1.97%  (p=0.008 n=5+5)
wuffs_jpeg_decode_30k_24bpp_progressive/clang11   309MB/s ± 0%   338MB/s ± 0%   +9.29%  (p=0.008 n=5+5)
wuffs_jpeg_decode_30k_24bpp_sequential/clang11   1.00GB/s ± 0%  1.01GB/s ± 0%   +1.31%  (p=0.008 n=5+5)
wuffs_jpeg_decode_77k_24bpp/clang11               827MB/s ± 0%   841MB/s ± 0%   +1.76%  (p=0.008 n=5+5)
wuffs_jpeg_decode_552k_24bpp_420/clang11          897MB/s ± 0%   913MB/s ± 0%   +1.86%  (p=0.008 n=5+5)
wuffs_jpeg_decode_552k_24bpp_444/clang11         1.10GB/s ± 0%  1.11GB/s ± 0%   +0.11%  (p=0.024 n=5+5)
wuffs_jpeg_decode_4002k_24bpp/clang11             900MB/s ± 0%   920MB/s ± 0%   +2.20%  (p=0.008 n=5+5)

wuffs_jpeg_decode_19k_8bpp/gcc10                  369MB/s ± 0%   349MB/s ± 0%   -5.45%  (p=0.008 n=5+5)
wuffs_jpeg_decode_30k_24bpp_progressive/gcc10     283MB/s ± 0%   328MB/s ± 0%  +15.76%  (p=0.008 n=5+5)
wuffs_jpeg_decode_30k_24bpp_sequential/gcc10      945MB/s ± 0%   925MB/s ± 0%   -2.12%  (p=0.008 n=5+5)
wuffs_jpeg_decode_77k_24bpp/gcc10                 769MB/s ± 0%   732MB/s ± 0%   -4.88%  (p=0.008 n=5+5)
wuffs_jpeg_decode_552k_24bpp_420/gcc10            842MB/s ± 0%   798MB/s ± 0%   -5.25%  (p=0.008 n=5+5)
wuffs_jpeg_decode_552k_24bpp_444/gcc10           1.01GB/s ± 0%  0.96GB/s ± 0%   -4.77%  (p=0.008 n=5+5)
wuffs_jpeg_decode_4002k_24bpp/gcc10               848MB/s ± 0%   806MB/s ± 0%   -4.96%  (p=0.008 n=5+5)
2023-08-19 21:18:53 +10:00
..
2019-12-20 00:52:23 +11:00
2023-04-08 14:57:52 +10:00

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.