From: David Ung <davidu@mips.com>
To: cgd@broadcom.com
Cc: gdb-patches@sources.redhat.com, nigel@mips.com
Subject: Re: MIPS32 / MIPS64 release 2 support in simulator
Date: Thu, 04 Nov 2004 13:53:00 -0000 [thread overview]
Message-ID: <1099576389.2778.90.camel@stockwell.mips.com> (raw)
In-Reply-To: <yov5d5yuojo4.fsf@xl-sj1-01.sj.broadcom.com>
On Wed, 2004-11-03 at 18:46, cgd@broadcom.com wrote:
> At Wed, 3 Nov 2004 16:57:42 +0000 (UTC), cgd@broadcom.com wrote:
> > > *mips32,mips64:
> >
> > These **must** be ...r2 or similar. Otherwise, they'll be included in
> > mips32/mip64 sims.
>
> So, more information about this: this ties in to where the new
> instructions are located.
>
> If we consider this a new ISA -- as the rest of the tools do, and as I
> think we probably want to do as well -- then:
>
> * the new instructions should go into mips.igen.
>
> * **all** instructions which are applicable to
> mips32r2/mips64r2 must be tagged with *mips64r2: and
> *mips32r2:.
>
> If we consider this as an ASE, then:
>
> * the new instructions should go into a new file, and
>
> * only the new instructions should be tagged with *mips64r2:
> and *mips32r2:.
>
>
> My personal incliation is that it should be treated as an ISA, just
> like MIPS32 and MIPS64 were (rather than as being additions to MIPS II
> or MIPS IV).
>
> If you disagree, i'm open to hearing arguments for your position.
Agree..
I shall update mips.igen with the new r2 instructions and then submit it
as a patch.
David.
next prev parent reply other threads:[~2004-11-04 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 15:26 David Ung
[not found] ` <mailpost.1099495587.2562@news-sj1-1>
2004-11-03 16:54 ` cgd
2004-11-03 16:57 ` cgd
[not found] ` <mailpost.1099501062.5136@news-sj1-1>
2004-11-03 19:01 ` cgd
2004-11-04 13:53 ` David Ung [this message]
[not found] ` <mailpost.1099576418.9773@news-sj1-1>
2004-11-04 17:46 ` cgd
2004-11-08 16:44 ` Andrew Cagney
2004-11-08 18:06 ` David Ung
2004-11-09 15:54 ` David Ung
2004-11-09 16:12 ` Andrew Cagney
2004-11-09 16:23 ` cgd
2004-11-09 17:00 ` Andrew Cagney
2004-11-09 17:38 ` cgd
2004-11-24 17:08 ` David Ung
2004-11-24 18:17 ` cgd
2005-05-18 18:11 ` [patch ping] " David Ung
2005-05-19 2:04 ` cgd
[not found] ` <mailpost.1116450142.2303@news-sj1-1>
2005-05-25 2:21 ` cgd
2005-05-26 22:27 ` cgd
2005-05-27 14:38 ` David Ung
2004-11-09 23:36 ` Nigel Stephens
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=1099576389.2778.90.camel@stockwell.mips.com \
--to=davidu@mips.com \
--cc=cgd@broadcom.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nigel@mips.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