similar to: rsync 2.6.6pre1 released (ALERT: info on zlib security flaw)

Hi! TL;DR WDYT of adding zlib decompression capabilities to LLVMObject library? ld.gold from GNU binutils has --compress-debug-sections=zlib option, which uses zlib to compress .debug_xxx sections and renames them to .zdebug_xxx. binutils (and GDB) support this properly, while LLVM command line tools don't: $ ld --version GNU gold (GNU Binutils for Ubuntu 2.22) 1.11 $ ./bin/clang++ -g a.cc

On Tue, Apr 16, 2013 at 8:31 PM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com>wrote: > >> Hi! >> >> TL;DR WDYT of adding zlib decompression capabilities to LLVMObject >> library? >> > >> ld.gold from GNU binutils has --compress-debug-sections=zlib option,

On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com>wrote: > Hi! > > TL;DR WDYT of adding zlib decompression capabilities to LLVMObject library? > > ld.gold from GNU binutils has --compress-debug-sections=zlib option, > which uses zlib to compress .debug_xxx sections and renames them to > .zdebug_xxx. > binutils (and GDB) support this properly,

On Tue, Apr 16, 2013 at 9:37 AM, Alexey Samsonov <samsonov at google.com> wrote: > > On Tue, Apr 16, 2013 at 8:31 PM, Michael Spencer <bigcheesegs at gmail.com> > wrote: >> >> On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com> >> wrote: >>> >>> Hi! >>> >>> TL;DR WDYT of adding zlib decompression

Just in case - do we want to link with libz.so installed in the system, or be self-contained and copy sources to LLVM repo? On Tue, Apr 16, 2013 at 10:48 PM, Eric Christopher <echristo at gmail.com>wrote: > On Tue, Apr 16, 2013 at 9:37 AM, Alexey Samsonov <samsonov at google.com> > wrote: > > > > On Tue, Apr 16, 2013 at 8:31 PM, Michael Spencer <bigcheesegs at

Dear All, I think I am confused about how I'd be able to use zlib starting with R 2.7.0. I just downloaded the latest development version, built it, etc, but I am not able to find the zlib.h that, I believe, R should place somewhere under "where/you/want/R/to/go" (from --prefix=/where/you/want/R/to/go). There seem to be entry points for zlib in the binary (e.g., grep -r gzopen ./

I just setup a new SSD with my laptop root filesystem, and at the time I though, "eh, I''ll just use zlib compression during the first copy, and then switch to lzo afterwards to maintain write speed when I''m using the laptop after the copy and reboot". Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed to boot slower than it did before with the

Hi Rui, What's the intended advantage for compressing the debug sections? - (i) Improved link time through smaller IO / (ii) Improved Load / startup time for the debugger / (iii) Smaller exe with debug info for distribution / disk space? For i) and ii) how much this is worth it depends on balance of storage bandwidth to compression (i) / decompression (ii) bandwidth. For spinning drives it

Historically we've done the former. The latter would require Chris wanting to do that. -eric On Tue, Apr 16, 2013 at 11:52 AM, Alexey Samsonov <samsonov at google.com> wrote: > Just in case - do we want to link with libz.so installed in the system, or > be self-contained and copy sources to LLVM repo? > > > On Tue, Apr 16, 2013 at 10:48 PM, Eric Christopher <echristo

> As to (3), in most cases, I believe it is rare to distribute executables with debug info widely > I think it is at least less important than (1). Agreed. > I think (1) is definitely the case, and that's also true for a distributed build system with which a lot of object files are copied between machines. > My suggestion was to use compression level 9 when both -O2 and

Not really, as well as some sensitivity to the input data overall performance of the link with compression will depend on how this is implemented in lld - how is it parallelized? How is it chunked? Is it effectively pipelined with IO? Or, I wouldn't feel comfortable being able to make a recommendation to our end-users on whether to use this option or not based on my existing extensive

Hi, may be someone has already done that: Do you have a script(?) tool which shows the efficiency of the mail compression if zlib is used? Something that shows the uncompressed size vrs. the compressed. Thanks for hints! /G?tz -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5571 bytes Desc: S/MIME

SSH.COM says their SSH2 is not vulnerable to the ZLIB problem even though they use the library (details below). Can OpenSSH say the same thing? In either case, it seems like there ought to be an openssh-unix-announce message about what the situation is. I may have missed it, but I don't believe there was one. Yes, openssh doesn't have its own copy of zlib source but it would still be

I've noticed that maildir IMAP COPY commands can generate invalid dovecot.index entries when all seven of the following are true: - The zlib plugin is enabled; - The zlib_save/zlib_save_level options are NOT enabled; - The source message being copied is compressed; - The mail_log plugin is logging "copy" events; - The mail_log_fields setting includes at least one message header; -

On 3/15/16 10:13 AM, Sven Hartge wrote: > I don't have a script, but I can provide some numbers. I did a test with > a server for about 10.000 users and 2TB worth of mail, converting from > Maildir++ to mdbox with zlib (level = 6) and had a final size of 1TB, so > 2:1 reduction. These numbers roughly match my results. About 6 TB of mail compresses down to about 3 TB. The

Also not an expert, but would it make sense for this to be configurable at a fine-grained level, perhaps with another option, or an extension to the compress-debug-sections switch interface? That way users who care about the finer details can configure it themselves. And we should pick sensible options for the default. James On 2 August 2018 at 11:08, Pavel Labath via llvm-dev < llvm-dev at

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

Hey Folks, I''ve written a script to generate a list of all files on a machine, then zip the results. ?I''m going to stick a web front end on it, and use it to audit some file servers. The problem is that the ZIP compression/decompression isn''t working, but its not what you might think. ?The script completes, but seems to not actually write anything. Here is a short

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

Attached is a zlib advisory and a debug dump of ssh with compression enabled. Most of the debug is superflous, so I have underlined the two points to look at. When creating an ssh connection, compression on the line is done *before* authentication -- This means an unauthorized attacker could, conceivable, leverage root access by connecting with to the ssh server requesting zlib compression and