From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Nick Clifton <nickc@redhat.com>,
Cary Coutant <ccoutant@google.com>,
Binutils <binutils@sourceware.org>
Subject: Re: Fwd: PATCH: Extend .zdebug section support to binutils and ld
Date: Tue, 02 Nov 2010 22:16:00 -0000 [thread overview]
Message-ID: <AANLkTimn7YW6CSX_pW_QPJxTKBG=AgHPa66EVCBy0caj@mail.gmail.com> (raw)
In-Reply-To: <20101102215926.GK26513@bubble.grove.modra.org>
On Tue, Nov 2, 2010 at 2:59 PM, Alan Modra <amodra@gmail.com> wrote:
> On Tue, Nov 02, 2010 at 05:59:35AM -0700, H.J. Lu wrote:
>> I don't think they are all caused by my compress patch.
>
> Perhaps not. I didn't check them all.
>
>> Most of compress failures are due to linker script. I will
>> submit a patch to update linker scripts.
>
> A large number remain due to BFD_COMPRESS/BFD_DECOMPRESS. objdump -x
> displays bfd->flags. I think that to fix this properly you should
Which tests fails because of BFD_COMPRESS/BFD_DECOMPRESS?
> store the new compress controls in two single-bit fields. (See end of
> struct bfd.)
>
It is easier to use the flags field. Otherwise, I need to update
more places.
--
H.J.
next prev parent reply other threads:[~2010-11-02 22:16 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 ` Fwd: " Cary Coutant
2010-10-28 14:50 ` 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 [this message]
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='AANLkTimn7YW6CSX_pW_QPJxTKBG=AgHPa66EVCBy0caj@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=nickc@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).