From: "H.J. Lu" <hjl.tools@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Cary Coutant <ccoutant@google.com>,
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 13:36:00 -0000 [thread overview]
Message-ID: <CAMe9rOpmdUhHFF22k+YoB86rXdQ0xEE+eskqtrEwpu7NXxDzrw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOp+1NzmihCXZODJ7TW+y9uFCxSi_cVkwKR3=X7+KCv68g@mail.gmail.com>
On Fri, Mar 20, 2015 at 5:07 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Fri, Mar 20, 2015 at 2:01 AM, Pedro Alves <palves@redhat.com> wrote:
>> 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-gabi]
>>
>
> I will go with this one and "zlib" will be the same as "zlib-gnu" for now.
>
I implemented it on users/hjl/compressed branch. Any feedbacks?
Thanks.
--
H.J.
next prev parent reply other threads:[~2015-03-20 13:36 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
2015-03-20 12:07 ` H.J. Lu
2015-03-20 13:36 ` H.J. Lu [this message]
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=CAMe9rOpmdUhHFF22k+YoB86rXdQ0xEE+eskqtrEwpu7NXxDzrw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).