Files
wuffs/release/c
Nigel Tao 010df42d75 Have std/lzw always rewind excess bits
I'm not sure of the underlying reason for the lzw/gcc benchmark anomaly
(the gif/gcc numbers don't change), but it's the same mystery as commit
ecb3995 `Tweak how std/lzw yields "short read"`.

name                                    old speed      new speed      delta

wuffs_lzw_decode_20k/clang               223MB/s ± 0%   214MB/s ± 0%   -3.96%  (p=0.008 n=5+5)
wuffs_lzw_decode_100k/clang              385MB/s ± 0%   369MB/s ± 0%   -4.15%  (p=0.008 n=5+5)

wuffs_lzw_decode_20k/gcc                 186MB/s ± 1%   232MB/s ± 1%  +24.41%  (p=0.008 n=5+5)
wuffs_lzw_decode_100k/gcc                224MB/s ± 1%   384MB/s ± 1%  +71.81%  (p=0.008 n=5+5)

wuffs_gif_decode_1k_bw/clang             238MB/s ± 1%   236MB/s ± 0%     ~     (p=0.222 n=5+5)
wuffs_gif_decode_1k_color/clang          124MB/s ± 0%   118MB/s ± 1%   -4.75%  (p=0.008 n=5+5)
wuffs_gif_decode_10k_bgra/clang          596MB/s ± 0%   562MB/s ± 0%   -5.71%  (p=0.008 n=5+5)
wuffs_gif_decode_10k_indexed/clang       159MB/s ± 0%   149MB/s ± 0%   -6.42%  (p=0.008 n=5+5)
wuffs_gif_decode_100k_artificial/clang   492MB/s ± 1%   487MB/s ± 0%   -0.98%  (p=0.008 n=5+5)
wuffs_gif_decode_100k_realistic/clang    192MB/s ± 0%   183MB/s ± 0%   -5.07%  (p=0.008 n=5+5)
wuffs_gif_decode_1000k/clang             195MB/s ± 0%   185MB/s ± 0%   -4.93%  (p=0.008 n=5+5)
wuffs_gif_decode_anim_screencap/clang   1.01GB/s ± 1%  1.02GB/s ± 0%   +1.25%  (p=0.008 n=5+5)

wuffs_gif_decode_1k_bw/gcc               247MB/s ± 0%   250MB/s ± 0%   +1.26%  (p=0.008 n=5+5)
wuffs_gif_decode_1k_color/gcc            131MB/s ± 2%   133MB/s ± 0%     ~     (p=0.151 n=5+5)
wuffs_gif_decode_10k_bgra/gcc            541MB/s ± 1%   543MB/s ± 1%     ~     (p=0.548 n=5+5)
wuffs_gif_decode_10k_indexed/gcc         167MB/s ± 0%   167MB/s ± 1%     ~     (p=0.730 n=4+5)
wuffs_gif_decode_100k_artificial/gcc     469MB/s ± 0%   465MB/s ± 1%   -0.78%  (p=0.016 n=4+5)
wuffs_gif_decode_100k_realistic/gcc      190MB/s ± 0%   190MB/s ± 0%   -0.34%  (p=0.032 n=4+5)
wuffs_gif_decode_1000k/gcc               193MB/s ± 1%   192MB/s ± 1%     ~     (p=0.556 n=4+5)
wuffs_gif_decode_anim_screencap/gcc      995MB/s ± 1%   995MB/s ± 1%     ~     (p=0.841 n=5+5)
2018-12-22 14:05:34 +11:00
..
2018-07-21 09:28:48 +10:00
2018-12-08 16:09:45 +11:00

Wuffs ships as a "single file C library", also known as a "header file library".

To use Wuffs 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 version (but not the unsupported snapshot), with a filename like wuffs-vMAJOR.MINOR.h 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.