public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: echristo@redhat.com, cgd@broadcom.com, newlib@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: [patch] modify crt0.S for 64-bit address targets
Date: Wed, 06 Apr 2005 19:35:00 -0000	[thread overview]
Message-ID: <m38y3vvgvf.fsf@gossamer.airs.com> (raw)
In-Reply-To: <16980.14602.380063.574194@gargle.gargle.HOWL>

Paul Koning <pkoning@equallogic.com> writes:

>  Eric> Assuredly this is the case. I think the problem might be from
>  Eric> using the ori instead of addi for the address. ori zero extends
>  Eric> the constant, addi sign extends. IIRC all addresses should be
>  Eric> sign extended and as such we should be using addi here yes? I
>  Eric> seem to recall that we changed this a while back because the
>  Eric> ori was some small amount faster.
> 
> Faster?  On a RISC machine?  Seems odd.

I think Eric is reversed, actually.  There was a MIPS processor which
had two add units but only one logical unit.  Therefore, on average,
on that processor, add was faster.  That fact led to this change:

Tue Jul 11 11:49:49 1995  Ian Lance Taylor  <ian@cygnus.com>

	* mips-opc.c (mips_opcodes): For the move pseudo-op, prefer daddu
	if ISA 3 and addu otherwise, replacing or, since some MIPS chips
	have multiple add units but only a single logical unit.

Ian

  reply	other threads:[~2005-04-06 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1112768205.5493.2.camel@localhost.localdomain>
     [not found] ` <mailpost.1112768909.17118@news-sj1-1>
2005-04-06  6:49   ` cgd
2005-04-06 11:05     ` Maciej W. Rozycki
2005-04-06 11:22       ` Thiemo Seufer
2005-04-06 14:40         ` Maciej W. Rozycki
2005-04-06 18:37     ` Eric Christopher
2005-04-06 19:31       ` Paul Koning
2005-04-06 19:35         ` Ian Lance Taylor [this message]
2005-04-06 21:35         ` Eric Christopher
2005-04-06 18:51 cgd
2005-04-06 19:01 ` Eric Christopher

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=m38y3vvgvf.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=echristo@redhat.com \
    --cc=newlib@sources.redhat.com \
    --cc=pkoning@equallogic.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).