public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: Andrew Bennett <Andrew.Bennett@imgtec.com>,
	"binutils@sourceware.org"	<binutils@sourceware.org>
Subject: Re: [PATCH] Add MIPS ufr macro instruction
Date: Fri, 13 Dec 2013 18:36:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1312131823410.19368@tp.orcam.me.uk> (raw)
In-Reply-To: <87vbysiu3a.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>

On Fri, 13 Dec 2013, Richard Sandiford wrote:

> Looks good, thanks, but is there any reason not to use mips_cp1_names_mips3264
> for all MIPS32 and MIPS64 targets?  I realise some of them don't have an FPU,
> but if we see (presumably emulated) FPU instructions anyway, then I think we
> might as well follow the architecture names for the registers.

 Rev. 1 FPUs only had the FIR, FCCR, FEXR, FENR and FCSR registers.  Older 
ISAs only had the FIR and FCSR registers.  How about we have separate 
lists just as with CP0?  Furthermore I don't think these additional lists 
should be a prerequisite for the acceptance of this patch.

> E.g.:
> 
> Andrew Bennett <Andrew.Bennett@imgtec.com> writes:
> > @@ -525,43 +571,43 @@ const struct mips_arch_choice mips_arch_choices[] =
> >    { "sb1",	1, bfd_mach_mips_sb1, CPU_SB1,
> >      ISA_MIPS64 | INSN_SB1,  ASE_MIPS3D,
> >      mips_cp0_names_sb1,
> >      mips_cp0sel_names_sb1, ARRAY_SIZE (mips_cp0sel_names_sb1),
> > -    mips_hwr_names_numeric },
> > +    mips_cp1_names_numeric, mips_hwr_names_numeric },
> 
> SB1 did have an FPU.

 It was rev. 1 however.

> If you agree, then the patch is OK with every ISA_MIPS32* and ISA_MIPS64*
> entry having mips_cp1_names_mips3264.  If not then let me know :-)

 Shouldn't there be a complementing GAS part though?

  Maciej

  reply	other threads:[~2013-12-13 18:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 14:04 Andrew Bennett
2013-11-08 17:33 ` David Daney
2013-11-09 11:27 ` Richard Sandiford
2013-11-14  9:12   ` Richard Sandiford
2013-11-14 12:42     ` Andrew Bennett
2013-11-20 16:14       ` Andrew Bennett
2013-11-24 18:32         ` Richard Sandiford
2013-11-25  8:40           ` Maciej W. Rozycki
2013-12-09 15:38             ` Andrew Bennett
2013-12-10 12:38               ` Richard Sandiford
2013-12-11 12:20                 ` Andrew Bennett
2013-12-13 16:39                   ` Richard Sandiford
2013-12-13 18:36                     ` Maciej W. Rozycki [this message]
2013-12-14 10:13                       ` Richard Sandiford
2014-01-10 18:12                         ` Maciej W. Rozycki
2013-12-14 18:51                     ` Andrew Bennett

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=alpine.DEB.1.10.1312131823410.19368@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=Andrew.Bennett@imgtec.com \
    --cc=binutils@sourceware.org \
    --cc=rdsandiford@googlemail.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).