public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: binutils@sources.redhat.com, nigel@mips.com
Subject: Re: [PATCH] Support for MIPS16 HI16/LO16 relocations
Date: Thu, 17 Feb 2005 13:24:00 -0000	[thread overview]
Message-ID: <1108616618.4149.8.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0502161404540.12803@perivale.mips.com>


>  Hmm, I've built and run the testsuite for your failing target using an 
> unmodified checkout as of now and I cannot reproduce your failures.  In 
> fact the source lines you've reported do not even contain BFD_ASSERT() 
> statements.  Can you please verify you have a consistent snapshot?

I'm apparently nuts. Sorry.

Don't see it anymore.

-eric

      reply	other threads:[~2005-02-17  5:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 21:54 Maciej W. Rozycki
2005-02-16  1:37 ` Thiemo Seufer
2005-02-16  7:03 ` Eric Christopher
2005-02-16 20:11   ` Maciej W. Rozycki
2005-02-17 13:24     ` Eric Christopher [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=1108616618.4149.8.camel@localhost.localdomain \
    --to=echristo@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=macro@mips.com \
    --cc=nigel@mips.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).