public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Cary Coutant <ccoutant@google.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>
Subject: Fwd: PATCH: Extend .zdebug section support to binutils and ld
Date: Tue, 26 Oct 2010 17:07:00 -0000	[thread overview]
Message-ID: <AANLkTimy34mCiihdJJ-dsOyWvuh_kaQr8SmTmv=XDZiU@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=gL5SysVBSdhcDsM5JFLr4SGTSaT3-9YsSFghu@mail.gmail.com>

[this time with the right email for Alan...]


---------- Forwarded message ----------
From: Cary Coutant <ccoutant@google.com>
Date: Tue, Oct 26, 2010 at 1:03 PM
Subject: Re: PATCH: Extend .zdebug section support to binutils and ld
To: binutils@sourceware.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@bigpond.net.au>


Ping? I'd like to see binutils and gnu ld supporting compressed debug sections.

-cary


On Fri, Aug 6, 2010 at 1:37 PM, Cary Coutant <ccoutant@google.com> wrote:
> On Thu, Jul 22, 2010 at 12:59 PM, Daniel Jacobowitz
> <dan@codesourcery.com> wrote:
>> That doesn't tell me anything.  What is the right thing to do, now
>> that you've made binutils do it?  Do you have to uncompress the
>> section and then apply relocations to it?
>>
>> If you do, there's no separate issue - don't check this in unless
>> objects are marked in such a way that other tools will immediately
>> reject them.
>
> Yes, it would be an improvement to mark compressed sections with a new
> section type and SHF_OS_NONCONFORMING, but the ".zdebug" mechanism is
> already there right now, and it would be nice to have this patch to
> make the utilities work with what the assembler is producing today.
> The renaming convention was established a couple of years ago as a
> cheap way of preventing unaware tools of choking on these sections --
> this patch fixes a bug that was introduced then (trying to apply
> relocations before decompressing), but not actually exposed until gas
> started generating relocatable compressed sections.
>
> I'm not sure I understand why this patch should be held up until we
> implement a more foolproof mechanism. Adding this patch shouldn't
> prevent us from pursuing the better solution, but it will improve
> things in the meantime.
>
> -cary
>

  reply	other threads:[~2010-10-26 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 16:55 H.J. Lu
2010-07-22 17:06 ` Daniel Jacobowitz
2010-07-22 17:09   ` H.J. Lu
2010-07-22 20:00     ` Daniel Jacobowitz
2010-07-22 20:26       ` H.J. Lu
2010-08-06 17:58       ` Cary Coutant
2010-10-26 17:03         ` Cary Coutant
2010-10-26 17:07           ` Cary Coutant [this message]
2010-10-28 14:50             ` Fwd: " Nick Clifton
2010-11-01 22:09               ` Alan Modra
2010-11-02 12:59                 ` H.J. Lu
2010-11-02 21:59                   ` Alan Modra
2010-11-02 22:16                     ` H.J. Lu
2010-11-02 22:57                       ` Alan Modra
2010-11-02 23:06                         ` H.J. Lu
2010-11-02 23:55                           ` Alan Modra
2010-11-03  0:33                             ` H.J. Lu
2010-11-03  0:46                               ` H.J. Lu
2010-11-03  3:22                               ` Alan Modra
2010-11-12 22:15               ` 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='AANLkTimy34mCiihdJJ-dsOyWvuh_kaQr8SmTmv=XDZiU@mail.gmail.com' \
    --to=ccoutant@google.com \
    --cc=amodra@gmail.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).