| 5ccb2b3621f633708eb3ae1fd0f27f88bdb32a9d |
|
29-Jan-2015 |
Narayan Kamath <narayan@google.com> |
Fix deflater in / out counts for inputs > 4G.
The underlying inflate & deflate can process any amount of data
correctly, since the protocol is chunk based (the size of each
chunk is limited to 32 bits, usually) and there is no limit to
the number of chunks.
On LP32, the stream counters are limited to 32 bit counts and
the manual recommends that the caller maintain their own counters
to support larger counts.
<quote>
Note however that the strm.total_in and strm_total_out counters may be
limited to 4 GB. These counters are provided as a convenience and are
not used internally by inflate() or deflate(). The application can
easily set up its own counters updated after each call of inflate()
or deflate() to count beyond 4 GB.
</quote>
Change-Id: I066e1141935154773360c1b9f94c56bd604f8474
|
| b3aacde3d8af759ee4a7b395c636ea360547d92d |
|
05-Nov-2014 |
Ian Rogers <irogers@google.com> |
Move from UniquePtr to std::unique_ptr.
Switch from stlport to libcxx as stlport lacks std::unique_ptr.
Change-Id: I45a3588a8ecf4689521f1df6654ed279a6d0669e
|
| 011ed31c4d057d973931fa81a09d8c576a72d82a |
|
22-Aug-2013 |
Kenny Root <kroot@google.com> |
Better error messages for zlib errors
Most of the zlib inflater errors had a really descriptive name like
"data error," but more descriptive errors are put into the "msg" field
of the z_stream structure. Use that for error messages instead so we get
the underlying cause of the data error.
Additionally split out the code for ZipUtilities from the header into a
separate source file so things using NativeZipStream don't have to
forward declare.
(cherry picked from commit 2e6a64542c52490d89476bfd1b10b1938a8a0e99)
Bug: 10424836
Change-Id: Ifc12645b37f7aabc700e6a0766dee55b4c3609a0
|
| 2e6a64542c52490d89476bfd1b10b1938a8a0e99 |
|
22-Aug-2013 |
Kenny Root <kroot@google.com> |
Better error messages for zlib errors
Most of the zlib inflater errors had a really descriptive name like
"data error," but more descriptive errors are put into the "msg" field
of the z_stream structure. Use that for error messages instead so we get
the underlying cause of the data error.
Additionally split out the code for ZipUtilities from the header into a
separate source file so things using NativeZipStream don't have to
forward declare.
Change-Id: Ifc12645b37f7aabc700e6a0766dee55b4c3609a0
|
| 3aac4ddc4d17c07fa8b4908069d23d5401a77993 |
|
05-Feb-2013 |
Elliott Hughes <enh@google.com> |
Add icu4c-backed transliteration.
Change-Id: I4194810646a2a0661331aaf941fb5f99ce7758b1
|