public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: Re: RFC: Add support for SHF_COMPRESSED
Date: Thu, 19 Mar 2015 18:50:00 -0000	[thread overview]
Message-ID: <CAMe9rOqNoECma=Xhy4wdmX=ZXegvMnbL6nW1yyWtxZVsM+V8+g@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4qwgFbz_jF5hE1WeaKfhuYPD0iDerEiu4Dzx3KMtSdnUw@mail.gmail.com>

On Thu, Mar 19, 2015 at 11:18 AM, Cary Coutant <ccoutant@google.com> wrote:
>> I added --compressed-debug-sections=[none|zlib] to as and
>> objcopy.  I updated gold to decompress SHF_COMPRESSED
>> section.  I didn't add --compressed-debug-sections=[none|zlib]
>> to gold since I don't know if this name is a final choice nor
>> gold maintainers want such an option.
>
> objcopy, gas, and gold already have the --compress-debug-sections
> option (though only gold takes "=[none|zlib]" as a parameter; objcopy
> and gas always use zlib, and spell the negative as
> --nocompress-debug-sections).
>
> I don't see any point in adding another option, especially one spelled
> so similarly -- just use the existing option and make it generate the
> new form, after all the consumers understand both formats. (And I
> prefer a verb to an adjective.)

Which consumers do we care?

> If you want the option to generate either format, how about something
> like "--compress-debug-sections=[none|zlib|zlib-old|zlib-new]"? (Where
> "zlib" would generate the old for a while, then we'd switch it to the
> new after some time.
>

I will do it.

Thanks.


-- 
H.J.

  reply	other threads:[~2015-03-19 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 15:31 H.J. Lu
2015-03-13 16:05 ` Jan Beulich
2015-03-13 16:13   ` H.J. Lu
2015-03-13 16:19     ` Jan Beulich
2015-03-18 21:29       ` H.J. Lu
2015-03-19 18:19         ` Cary Coutant
2015-03-19 18:50           ` H.J. Lu [this message]
2015-03-20  9:01           ` Pedro Alves
2015-03-20 12:07             ` H.J. Lu
2015-03-20 13:36               ` H.J. Lu
2015-03-23 12:31                 ` H.J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMe9rOqNoECma=Xhy4wdmX=ZXegvMnbL6nW1yyWtxZVsM+V8+g@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).