Karlson2k

Thanks for the new release, Igor. And special thanks for the source code in .tar.xz format! Happy New Year!

Pavel, maybe it makes sense to add a special parameter to override memory restrictions, so advanced users would have a choice? Some users may have swap located on very fast devices (as it was pointed here), others may be just OK if compression will take hours or days. Let's give users a choice, leaving default memory amount check enabled if no special parameter is used. I think it could be a good compromise.

These lines confuse package maintainers. It's unclear whether they indicate some error condition or just normal (I assume that they are just kind of debugging for compile-time). I would suggest to either completely disable pragma messages without defined _DEBUG macro or make them more readable like Compiling SSE41 version of LzFind().

What's happen on Gentoo if the package is compiled without -noexestack: * QA Notice: The following files contain writable and executable sections * Files with such sections will not work properly (or at all!) on some * architectures/operating systems. A bug should be filed at * https://bugs.gentoo.org/ to make sure the issue is fixed. * For more information, see: * * https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart * * Please include the following list of files in your report: * Note: Bugs...

What's happen on Gentoo if the package is compiled without -noexestack: * QA Notice: The following files contain writable and executable sections * Files with such sections will not work properly (or at all!) on some * architectures/operating systems. A bug should be filed at * https://bugs.gentoo.org/ to make sure the issue is fixed. * For more information, see: * * https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart * * Please include the following list of files in your report: * Note: Bugs...

Hi Igor. Gentoo built-in QA check detected that all binaries with x86/amd64 assembler code has "stack executable" flags. I've checked assembler-generated .o files. $ readelf -S LzFindOpt.o There are 7 section headers, starting at offset 0x40: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .text PROGBITS 0000000000000000 00000200 0000000000000000 0000000000000000 AX 0 0 16 [ 2] .data...

Hi Igor. Gentoo built-in QA check detected that all binaries with x86/amd64 assembler code has "stack executable" flags. I've checked assembler-generated .o files. $ readelf -S LzFindOpt.o There are 7 section headers, starting at offset 0x40: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .text PROGBITS 0000000000000000 00000200 0000000000000000 0000000000000000 AX 0 0 16 [ 2] .data...

Hi Igor. Gentoo built-in QA check detected that all binaries with x86/amd64 assembler code has "stack executable" flags. I've checked assembler-generated .o files. $ readelf -S LzFindOpt.o There are 7 section headers, starting at offset 0x40: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .text PROGBITS 0000000000000000 00000200 0000000000000000 0000000000000000 AX 0 0 16 [ 2] .data...