From: Zack Weinberg <zack@codesourcery.com>
To: Christian Joensson <christian.joensson@gmail.com>
Cc: binutils <binutils@sources.redhat.com>
Subject: Re: Results for 2.15.94 20050217 testsuite on sparc-unknown-linux-gnu
Date: Fri, 18 Feb 2005 04:34:00 -0000 [thread overview]
Message-ID: <87vf8qbp7p.fsf@codesourcery.com> (raw)
In-Reply-To: <20050218015423.GJ10128@bubble.modra.org> (Alan Modra's message of "Fri, 18 Feb 2005 12:24:23 +1030")
Alan Modra <amodra@bigpond.net.au> writes:
> On Thu, Feb 17, 2005 at 10:33:30PM +0100, Christian Joensson wrote:
>> FAIL: ld-scripts/align2a
>> FAIL: ld-scripts/align2b
>
> Memo to self and Nick: Just because Zack is an accomplished gcc hacker
> doesn't mean he knows what he's doing in binutils!
Blargh. Sorry about that. You're quite right, I don't know what I'm
doing in binutils. I've been trying to avoid it, in fact, but
sometimes I get stuck with these customer bugs...
zw
prev parent reply other threads:[~2005-02-18 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 0:35 Christian Joensson
2005-02-18 2:02 ` Christian Joensson
2005-02-18 2:58 ` Alan Modra
2005-02-18 4:34 ` Zack Weinberg [this message]
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=87vf8qbp7p.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=christian.joensson@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).