Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nigel Stephens <nigel@mips.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
	Dmitriy Tochansky <toch@dfpost.ru>,
	linux-mips@linux-mips.org
Subject: Re: Strange instruction
Date: Thu, 14 Oct 2004 13:16:50 +0100	[thread overview]
Message-ID: <416E6E32.5080009@mips.com> (raw)
In-Reply-To: <20041014121242.GA1398@rembrandt.csv.ica.uni-stuttgart.de>



Thiemo Seufer wrote:

>
>
>GNU as has "move" as builtin macro which is expanded differently for
>32 and 64 bit mode. This simplifies the task of writing code for both
>models. Unfortunately the expansion was broken for a while and
>generated always the 64 bit version if the toolchain was 64bit
>_capable_. IIRC this was fixed in the early 2.14 timeframe.
>
>
>  
>

Wouldn't it be safer, as Kevin suggests, for the "move" macro to 
generate "or $rd,$0,$rs", since that will work correctly in either mode?

Nigel

>  
>

  reply	other threads:[~2004-10-14 12:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 11:53 Strange instruction Dmitriy Tochansky
2004-10-14  8:34 ` Kevin D. Kissell
2004-10-14  8:34   ` Kevin D. Kissell
2004-10-14 12:12   ` Thiemo Seufer
2004-10-14 12:16     ` Nigel Stephens [this message]
2004-10-14 12:36       ` Thiemo Seufer
2004-10-14 13:12         ` Kevin D. Kissell
2004-10-14 13:12           ` Kevin D. Kissell
2004-10-14 13:34           ` Thiemo Seufer
2004-10-14  8:45 ` Fuxin Zhang
     [not found]   ` <000b01c4b1da$6e049f00$10eca8c0@grendel>
     [not found]     ` <416E5B62.8050508@ict.ac.cn>
2004-10-14 11:13       ` Kevin D. Kissell
2004-10-14 11:13         ` Kevin D. Kissell
2004-10-14 13:45 ` Dan Malek
2004-10-14 19:06   ` Dan Malek

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=416E6E32.5080009@mips.com \
    --to=nigel@mips.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=toch@dfpost.ru \
    /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