Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Cary Coutant <ccoutant@google.com>, "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	Binutils <binutils@sourceware.org>,
	       GDB <gdb@sourceware.org>
Subject: Re: RFC: Add support for SHF_COMPRESSED
Date: Fri, 20 Mar 2015 09:01:00 -0000	[thread overview]
Message-ID: <550BE1F8.7030405@redhat.com> (raw)
In-Reply-To: <CAHACq4qwgFbz_jF5hE1WeaKfhuYPD0iDerEiu4Dzx3KMtSdnUw@mail.gmail.com>

On 03/19/2015 06:18 PM, Cary Coutant wrote:
> 
> 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.

Can we please find terms that describe that "old" and "new" mean and
use those instead?  "new" will eventually be old news too.
We did that mistake with "--enable-new-dtags", let's not repeat it.

For example:

 --compress-debug-sections=[none|zlib|zlib-gnu|zlib-shf-compressed]
 --compress-debug-sections=[none|zlib|zlib-gnu|zlib-shf]
 --compress-debug-sections=[none|zlib|zlib-gnu|zlib-gabi]

or even:

 --compress-debug-sections=[none|zlib|zlib-v1|zlib-v2]

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-03-20  9:01 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
2015-03-20  9:01           ` Pedro Alves [this message]
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=550BE1F8.7030405@redhat.com \
    --to=palves@redhat.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.com \
    /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