https://sourceware.org/bugzilla/show_bug.cgi?id=19109
--- Comment #27 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Nick Clifton from comment #26)
> Hi H.J.
>
> > A patch to add
> >
> > --enable-compressed-debug-sections={all,gas,gold,ld}
> > Enable compressed debug sections for gas, gold or ld
> > by default
>
> Before the patch goes in I would like to check a few things:
>
> * If compression is enabled for gas but not ld for example,
> does this mean that the linker will uncompress compressed
> debug sections when it writes them out ? Or rather, is
Yes.
> that what configuring with --enable-compressed-debug-sections=gas
> implies ?
Yes.
> * What happens if the linker is given some input files containing
> compressed debug sections and some input files not containing
> compressed debug sections ? Is the output always compressed ?
Linker always decompresses any compressed debug sections when reading
input files and generates compressed debug sections in output when
--enable-compressed-debug-sections=all or
--enable-compressed-debug-sections=[gas,]ld[,gold] are used.
> * What advantage is gained by compressing debug sections, as opposed
> to splitting out the debug information and the compressing the whole
> debug file ?
How do you do that with .o files? As for executable/shared libraries,
it should be decided by users. In my case, I can compress debug sections
in as/ld and run them directly in gdb. I don't need to a separate step
to extract/compress debug info. I have many different versions of binutils
binaries laying around. Separate debug files will only lead to trouble for
me.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-binutils
