From: cgd@broadcom.com
To: "Richard Sandiford" <rsandifo@redhat.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, binutils@sources.redhat.com
Subject: Re: [patch] MIPS: Fix synthesized doubleword transfers (ping)
Date: Fri, 25 Feb 2005 02:17:00 -0000 [thread overview]
Message-ID: <yov5ll9d1ti3.fsf@xl-sj1-01.sj.broadcom.com> (raw)
In-Reply-To: <87oee9ha6p.fsf@firetop.home>
At Thu, 24 Feb 2005 22:20:30 +0000, Richard Sandiford wrote:
> cgd@broadcom.com writes:
> > At Thu, 24 Feb 2005 21:05:49 +0000 (UTC), "Richard Sandiford" wrote:
> >> I suppose bad things could happen if you composed an aligned
> >> address from an unaligned symbol and an unaligned offset,
> >> but is that allowed?
> >
> > yes, at least as far as the ISA is concerned.
>
> I don't follow. The ISA has no concept of symbols vs. offsets.
right, but to some degree symbol + offset -> base reg + offset, since
the offsets in the base regs come directly from the relocs.
the offsets in the instructions are 16-bit sign-extended values only
-- no scale.
some MIPS ISA levels, MIPS IV IIRC, had requirements that base reg
must be properly aligned, and that offset must be properly aligned.
(But IIRC those weren't present before MIPS IV, and aren't present in
MIPS32/MIPS64.)
chris
next prev parent reply other threads:[~2005-02-24 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 22:30 Maciej W. Rozycki
2005-02-24 22:57 ` Richard Sandiford
[not found] ` <mailpost.1109279149.22995@news-sj1-1>
2005-02-24 23:42 ` cgd
2005-02-25 0:04 ` Richard Sandiford
2005-02-25 1:23 ` Richard Sandiford
2005-02-25 2:17 ` cgd [this message]
2005-02-25 13:36 ` Richard Sandiford
2005-02-26 0:02 ` Maciej W. Rozycki
2005-02-25 20:25 ` Maciej W. Rozycki
2005-02-25 16:12 ` Richard Sandiford
2005-02-26 0:10 ` Maciej W. Rozycki
2005-03-02 2:22 ` Thiemo Seufer
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=yov5ll9d1ti3.fsf@xl-sj1-01.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=binutils@sources.redhat.com \
--cc=macro@linux-mips.org \
--cc=rsandifo@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).