Displaying 6 results from an estimated 6 matches for "shf_compressed".
2013 Apr 16
2
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...f we want debug info decompression to be transparent in
> LLVMObject or not. I'm leaning towards no since it's not part of the
> standard yet,
>
Yeah, I also think that decompression should be explicitly requested by the
user of LLVMObject.
> unless gold is actually using the SHF_COMPRESSED flag.
>
> I think it should be part of Object, but as an external API that is used
> when you find a section you know from external factors (the name matches
> some list) is compressed.
>
> - Michael Spencer
>
>
--
Alexey Samsonov, MSK
-------------- next part ----------...
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...ssion to be transparent in LLVMObject
>> or not. I'm leaning towards no since it's not part of the standard yet,
>
>
> Yeah, I also think that decompression should be explicitly requested by the
> user of LLVMObject.
>
>>
>> unless gold is actually using the SHF_COMPRESSED flag.
>>
>>
>> I think it should be part of Object, but as an external API that is used
>> when you find a section you know from external factors (the name matches
>> some list) is compressed.
>>
Definitely want the feature :)
I don't see SHF_COMPRESSED (un...
2013 Apr 16
2
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...t;> or not. I'm leaning towards no since it's not part of the standard yet,
> >
> >
> > Yeah, I also think that decompression should be explicitly requested by
> the
> > user of LLVMObject.
> >
> >>
> >> unless gold is actually using the SHF_COMPRESSED flag.
> >>
> >>
> >> I think it should be part of Object, but as an external API that is used
> >> when you find a section you know from external factors (the name matches
> >> some list) is compressed.
> >>
>
> Definitely want the feature...
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...s no since it's not part of the standard yet,
>> >
>> >
>> > Yeah, I also think that decompression should be explicitly requested by
>> > the
>> > user of LLVMObject.
>> >
>> >>
>> >> unless gold is actually using the SHF_COMPRESSED flag.
>> >>
>> >>
>> >> I think it should be part of Object, but as an external API that is
>> >> used
>> >> when you find a section you know from external factors (the name
>> >> matches
>> >> some list) is compres...
2013 Apr 16
0
[LLVMdev] RFC: Using zlib to decompress debug info sections.
...Alexey Samsonov, MSK
>
I'm not sure MemoryBuffer is the right place to do this either. I'm also
not sure if we want debug info decompression to be transparent in
LLVMObject or not. I'm leaning towards no since it's not part of the
standard yet, unless gold is actually using the SHF_COMPRESSED flag.
I think it should be part of Object, but as an external API that is used
when you find a section you know from external factors (the name matches
some list) is compressed.
- Michael Spencer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm...
2013 Apr 16
3
[LLVMdev] RFC: Using zlib to decompress debug info sections.
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