GoogleGit

  1. f6a298d  Release Snappy 1.1.2. R=jeff by snappy.mirrorbot@gmail.com - 5 months ago master
  2. 38de454  Fix public issue 82: Stop distributing benchmark data files that have unclear or unsuitable licensing. by snappy.mirrorbot@gmail.com - 5 months ago
  3. 6d76832  Add support for padding in the Snappy framed format. by snappy.mirrorbot@gmail.com - 9 months ago
  4. e512757  Release Snappy 1.1.1. by snappy.mirrorbot@gmail.com - 9 months ago
  5. 762bb32  Add autoconf tests for size_t and ssize_t. Sort-of resolves public issue 79; it would solve the problem if MSVC typically used autoconf. However, it gives a natural place (config.h) to put the typedef even for MSVC. by snappy.mirrorbot@gmail.com - 11 months ago
  6. f01cb89  When we compare the number of bytes produced with the offset for a backreference, make the signedness of the bytes produced clear, by sticking it into a size_t. This avoids a signed/unsigned compare warning from MSVC (public issue 71), and also is slightly clearer. by snappy.mirrorbot@gmail.com - 12 months ago
  7. 446f145  In the fast path for decompressing literals, instead of checking whether there's 16 bytes free and then checking right afterwards (when having subtracted the literal size) that there are now 5 bytes free, just check once for 21 bytes. This skips a compare and a branch; although it is easily predictable, it is still a few cycles on a fast path that we would like to get rid of. by snappy.mirrorbot@gmail.com - 1 year, 1 month ago
  8. 49fc9d9  Make the two IncrementalCopy* functions take in an ssize_t instead of a len, in order to avoid having to do 32-to-64-bit signed conversions on a hot path during decompression. (Also fixes some MSVC warnings, mentioned in public issue 75, but more of those remain.) They cannot be size_t because we expect them to go negative and test for that. by snappy.mirrorbot@gmail.com - 1 year, 1 month ago
  9. 35372c4  Add support for uncompressing to iovecs (scatter I/O). Windows does not have struct iovec defined anywhere, so we define our own version that's equal to what UNIX typically has. by snappy.mirrorbot@gmail.com - 1 year, 1 month ago
  10. 457b1b7  Some code reorganization needed for an internal change. by snappy.mirrorbot@gmail.com - 1 year, 1 month ago
  11. a18503d  Supports truncated test data in zippy benchmark. by snappy.mirrorbot@gmail.com - 1 year, 3 months ago
  12. 19c9869  Release Snappy 1.1.0. R=sanjay by snappy.mirrorbot@gmail.com - 1 year, 5 months ago
  13. 61b011f  Make ./snappy_unittest pass without "srcdir" being defined. by snappy.mirrorbot@gmail.com - 1 year, 5 months ago
  14. 8074527  Increase the Zippy block size from 32 kB to 64 kB, winning ~3% density while being effectively performance neutral. by snappy.mirrorbot@gmail.com - 1 year, 6 months ago
  15. de806bf  Adjust the Snappy open-source distribution for the changes in Google's internal file API. by snappy.mirrorbot@gmail.com - 1 year, 6 months ago
  16. 4a75599  Change a few ORs to additions where they don't matter. This helps the compiler use the LEA instruction more efficiently, since e.g. a + (b << 2) can be encoded as one instruction. Even more importantly, it can constant-fold the COPY_* enums together with the shifted negative constants, which also saves some instructions. (We don't need it for LITERAL, since it happens to be 0.) by snappy.mirrorbot@gmail.com - 1 year, 6 months ago
  17. bfbc527  Stop giving -Werror to automake, due to an incompatibility between current versions of libtool and automake on non-GNU platforms (e.g. Mac OS X). by snappy.mirrorbot@gmail.com - 1 year, 9 months ago
  18. 2f5d797  Fix public issue 66: Document GetUncompressedLength better, in particular that it leaves the source in a state that's not appropriate for RawUncompress. by snappy.mirrorbot@gmail.com - 1 year, 11 months ago
  19. 1640137  Fix public issue 64: Check for <sys/time.h> at configure time, since MSVC seemingly does not have it. by snappy.mirrorbot@gmail.com - 1 year, 12 months ago
  20. e726277  Handle the case where gettimeofday() goes backwards or returns the same value twice; it could cause division by zero in the unit test framework. (We already had one fix for this in place, but it was incomplete.) by snappy.mirrorbot@gmail.com - 2 years ago

Branches