Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: add fsrra and fsca instructions to SH simulator (resend)
Date: Fri, 31 Oct 2003 16:09:00 -0000	[thread overview]
Message-ID: <3FA2892B.1040102@redhat.com> (raw)
In-Reply-To: <200310311540.h9VFe5l08263@linsvr3.uk.superh.com>

>> > 2003-10-24  J"orn Rennecke <joern.rennecke@superh.com>
>> > 
>> > 	* interp.c (fsca_s, fsrra_s): New functions.
>> > 	* gencode.c (tab): Add entries for fsca and fsrra.
>> > 	(expand_opcode): Allow variable length n / m fields.
> 
>> 
>> Is it possible for this code to use the far more portable sim-fpu?
> 
> 
> The entire SH3E / SH4 simulator in sim/sh already uses native floating point,
> so making just these two instructions use sim-fpu would be pointless.
> 
> Converting the entire simulator would of course be possible, but I don't
> see any pressing need to do this now.  We have far more urgent issues
> with SH5 support in gcc and gdb that we should address first.

Can _just_ these new functions be implemented using sim-fpu?

Since the other code effectively pre-dates sim-fpu the fact that it 
didn't use it is understandable.  However, that doesn't excuse _new_ 
code from using the more robust sim-fpu.  You'll note that I carefully 
avoided suggesting that you should fix any of the old code - that would 
be unreasonable.

Andrew



  reply	other threads:[~2003-10-31 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 13:49 Joern Rennecke
2003-10-31 14:10 ` Andrew Cagney
2003-10-31 15:40   ` Joern Rennecke
2003-10-31 16:09     ` Andrew Cagney [this message]
2003-10-31 16:15       ` Joern Rennecke
2003-10-31 16:38         ` Andrew Cagney

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=3FA2892B.1040102@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joern.rennecke@superh.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