From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/5] MIPS/GAS: Fix o32 LD to the base register
Date: Mon, 01 Nov 2010 21:34:00 -0000 [thread overview]
Message-ID: <87mxpsd8y7.fsf@firetop.home> (raw)
In-Reply-To: <87vd4gd995.fsf@firetop.home> (Richard Sandiford's message of "Mon, 01 Nov 2010 21:28:06 +0000")
Richard Sandiford <rdsandiford@googlemail.com> writes:
> I still don't like the way that you're matching ECOFF and ELF offsets
> in a single test, allowing two load offsets when (for each format
> individually) only one offset is actually acceptable. But patch 5
> is OK nonetheless.
That is, the relevant parts of 5 are OK nonetheless (i.e. the
parts that cover patch 1). And I suppose that won't include any
of the ELF/ECOFF thing anyway.
Richard
prev parent reply other threads:[~2010-11-01 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 16:22 [PATCH 1/2] " Maciej W. Rozycki
2010-10-18 7:48 ` Richard Sandiford
2010-10-18 17:05 ` Maciej W. Rozycki
2010-10-31 22:46 ` [PATCH 1/5] " Maciej W. Rozycki
2010-11-01 21:28 ` Richard Sandiford
2010-11-01 21:34 ` Richard Sandiford [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=87mxpsd8y7.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.org \
--cc=macro@linux-mips.org \
/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).