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: Wed, 03 Nov 2010 00:46:00 -0000 [thread overview]
Message-ID: <AANLkTimB2Uh31CK6+b4jf67jkXQq7ywYBbX8cwE64=0e@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikL74ZD9gU3q-2zC-hcdcv31X4FXZSAcJLrPbm7@mail.gmail.com>
On Tue, Nov 2, 2010 at 5:33 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, Nov 2, 2010 at 4:54 PM, Alan Modra <amodra@gmail.com> wrote:
>> On Tue, Nov 02, 2010 at 04:06:42PM -0700, H.J. Lu wrote:
>>> I have no plan to investigate them unless they
>>> are caused by my compress change.
>>
>> These failures appeared soon after your compress patch was committed.
>> How can you know they were not caused by your commit unless you
>> investigate them? Do you expect me to clean up after you?
>>
>
> As I said, I couldn't reproduce your results, at least for hppa64-hp-hpux11.11
> target.
>
I will clear BFD_FLAGS_SAVED bits for objdump.
--
H.J.
next prev parent reply other threads:[~2010-11-03 0:46 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
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 [this message]
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='AANLkTimB2Uh31CK6+b4jf67jkXQq7ywYBbX8cwE64=0e@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).