public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <r.sandiford@redhat.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Why pass HAVE_32BIT_GPRS to OPCODE_IS_MEMBER?
Date: Tue, 07 Aug 2001 13:14:00 -0000	[thread overview]
Message-ID: <wvny9ovocer.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <20010807125931.A9923@lucon.org>

"H . J . Lu" <hjl@lucon.org> writes:

> The new gas generates different opcodes on Linux/mips. The change was
> introduced by the HAVE_32BIT_GPRS change. In include/opcode/mips.h
> 
> /* Test for membership in an ISA including chip specific ISAs.
>    INSN is pointer to an element of the opcode table; ISA is the
>    specified ISA to test against; and CPU is the CPU specific ISA
>    to test, or zero if no CPU specific ISA test is desired.
>    The gp32 arg is set when you need to force 32-bit register usage on
>    a machine with 64-bit registers; see the documentation under -mgp32
>    in the MIPS gas docs.  */
> 
> #define OPCODE_IS_MEMBER(insn, isa, cpu, gp32)                          \
> 
> I don't understand why the change was made. Here is a patch which
> restores the old opcodes. But I am not sure if it is 100% correct.
> Any comments?

I'm not sure why you want to make this change.  Because you want "addi" to be
used instead of "ori" for the move instruction?  It should be OK to change
mips-opc.c so that "addi" is used for -mgp32 if so.

There was discussion after I sent the patch of making the mtune option
decide which instruction is used for moves.  That sounded like a great idea,
so I held off making a mips-opc.c change myself.

Your patch seems to assume that "-mips2" and "-mips2 -mgp32" should give
different results, which doesn't make much sense to me.

Richard

  reply	other threads:[~2001-08-07 13:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 12:59 H . J . Lu
2001-08-07 13:14 ` Richard Sandiford [this message]
2001-08-07 13:23   ` H . J . Lu
2001-08-07 13:43 ` Thiemo Seufer
2001-08-07 14:06   ` H . J . Lu
2001-08-08  3:23     ` Thiemo Seufer
     [not found]   ` <mailpost.997217033.18854@postal.sibyte.com>
2001-08-07 14:54     ` cgd
2001-08-08  2:48       ` Thiemo Seufer
2001-08-08  5:22         ` Richard Sandiford
2001-08-08  5:31           ` Eric Christopher
2001-08-08  6:43             ` Thiemo Seufer
2001-08-08  6:47               ` Eric Christopher
2001-08-10  9:09             ` Richard Sandiford
2001-08-10  9:16               ` Eric Christopher
2001-08-08  3:30       ` Richard Sandiford
2001-08-08  4:05         ` 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=wvny9ovocer.fsf@talisman.cambridge.redhat.com \
    --to=r.sandiford@redhat.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=hjl@lucon.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).