xz.git - XZ Utils

Age	Commit message (Collapse)	Author	Files	Lines
2013-06-23	liblzma: Avoid a warning about a shadowed variable.	Lasse Collin	1	-2/+2
	On Mac OS X wait() is declared in <sys/wait.h> that we include one way or other so don't use "wait" as a variable name. Thanks to Christian Kujau.
2013-03-23	liblzma: Use lzma_block_buffer_bound64() in threaded encoder.	Lasse Collin	1	-16/+50
	Now it uses lzma_block_uncomp_encode() if the data doesn't fit into the space calculated by lzma_block_buffer_bound64().
2013-03-23	liblzma: Fix another deadlock in the threaded encoder.	Lasse Collin	1	-3/+6
	This race condition could cause a deadlock if lzma_end() was called before finishing the encoding. This can happen with xz with debugging enabled (non-debugging version doesn't call lzma_end() before exiting).
2012-12-14	Make the progress indicator smooth in threaded mode.	Lasse Collin	1	-5/+72
	This adds lzma_get_progress() to liblzma and takes advantage of it in xz. lzma_get_progress() collects progress information from the thread-specific structures so that fairly accurate progress information is available to applications. Adding a new function seemed to be a better way than making the information directly available in lzma_stream (like total_in and total_out are) because collecting the information requires locking mutexes. It's waste of time to do it more often than the up to date information is actually needed by an application.
2012-07-17	liblzma: Make the use of lzma_allocator const-correct.	Lasse Collin	1	-8/+8
	There is a tiny risk of causing breakage: If an application assigns lzma_stream.allocator to a non-const pointer, such code won't compile anymore. I don't know why anyone would do such a thing though, so in practice this shouldn't cause trouble. Thanks to Jan Kratochvil for the patch.
2011-10-23	liblzma: Fix a deadlock in the threaded encoder.	Lasse Collin	1	-1/+3
	It was triggered when reinitializing the encoder, e.g. when encoding two files.
2011-04-11	liblzma: Add lzma_stream_encoder_mt() for threaded compression.	Lasse Collin	1	-0/+1011
	This is the simplest method to do threading, which splits the uncompressed data into blocks and compresses them independently from each other. There's room for improvement especially to reduce the memory usage, but nevertheless, this is a good start.