public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
		Binutils <binutils@sourceware.org>,
	GDB <gdb-patches@sourceware.org>
Subject: Re: ping #3: [RFA] Add --with-libz-prefix option in config/zlib.m4
Date: Wed, 18 Feb 2015 22:03:00 -0000	[thread overview]
Message-ID: <CAMe9rOqwOa-kzOhaH_D84eGgYE0wV7k-J4jsxXUmHak4On_=aQ@mail.gmail.com> (raw)
In-Reply-To: <1424295643.23458.30.camel@bordewijk.wildebeest.org>

On Wed, Feb 18, 2015 at 1:40 PM, Mark Wielaard <mjw@redhat.com> wrote:
> On Wed, 2015-02-18 at 12:53 -0800, H.J. Lu wrote:
>> On Wed, Feb 18, 2015 at 12:32 PM, Mark Wielaard <mjw@redhat.com> wrote:
>> > That doesn't seem like a smart default. And why is is Linux/x86 only?
>> > Shouldn't that be something that is done explicitly by a distro
>> > configuring binutils after making sure it actually is beneficial
>> > (debuginfo is often compressed in a different way, on the package/file
>> > level or with dwz). And after making sure all tools actually work with
>> > it? There are various tools that don't handle the .zdebug format like
>> > valgrind. And at least elfutils has trouble with it for ET_REL files,
>> > like kernel modules, because relocations don't actually apply anymore to
>> > the section data as is (but only after the decompression).
>>
>> Now it becomes a monthly topic:
>>
>> https://sourceware.org/ml/binutils/2015-01/msg00089.html
>
> Thanks, I hadn't seen that before. Alan Modra makes some good points in
> that thread why it is not a good change:
> https://sourceware.org/ml/binutils/2015-01/msg00135.html
> Do people agree with that? And/Or can the change be reverted for now
> till there is agreement it is a desirable default?
>

It may not be a good idea for all targets.  If you find an issue
on Linux/x86, please file a bug binutils report.

Thanks.


-- 
H.J.

  reply	other threads:[~2015-02-18 22:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 14:46 Joel Brobecker
2015-01-07 16:01 ` Tristan Gingold
2015-01-07 17:02   ` Joel Brobecker
2015-02-19  7:55   ` Thomas Schwinge
2015-02-19  7:58     ` Thomas Schwinge
2015-01-21  7:49 ` ping: " Joel Brobecker
2015-01-21  8:22   ` Tristan Gingold
2015-01-21  8:33     ` Joel Brobecker
2015-02-04  3:57 ` ping^2: " Joel Brobecker
2015-02-18 12:09 ` ping #3: " Joel Brobecker
2015-02-18 12:56   ` H.J. Lu
2015-02-18 16:55     ` Mike Frysinger
2015-02-18 16:58       ` H.J. Lu
2015-02-18 19:44         ` Mike Frysinger
2015-02-18 19:52           ` H.J. Lu
2015-02-18 20:32             ` Mark Wielaard
2015-02-18 20:42               ` Jakub Jelinek
2015-02-18 20:53               ` H.J. Lu
2015-02-18 21:54                 ` Mark Wielaard
2015-02-18 22:03                   ` H.J. Lu [this message]
2015-02-18 22:21                     ` Mike Frysinger
2015-02-18 22:24                       ` H.J. Lu
2015-02-18 23:10                         ` Mike Frysinger
2015-02-19  7:17                     ` Mark Wielaard
2015-02-19 13:52                       ` H.J. Lu
2015-02-20  8:01                         ` Mark Wielaard
2015-02-18 17:00       ` Joel Sherrill
2015-02-19  2:42     ` Joel Brobecker

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='CAMe9rOqwOa-kzOhaH_D84eGgYE0wV7k-J4jsxXUmHak4On_=aQ@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mjw@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).