From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-36686-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 1780 invoked by alias); 4 Nov 2004 13:53:23 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 1767 invoked from network); 4 Nov 2004 13:53:22 -0000
Received: from unknown (HELO dmz.algor.co.uk) (62.254.210.145)
  by sourceware.org with SMTP; 4 Nov 2004 13:53:22 -0000
Received: from alg158.algor.co.uk ([62.254.210.158] helo=olympia.mips.com)
	by dmz.algor.co.uk with esmtp (Exim 3.35 #1 (Debian))
	id 1CPiBb-0001lw-00; Thu, 04 Nov 2004 14:01:59 +0000
Received: from stockwell.mips.com ([192.168.192.238])
	by olympia.mips.com with esmtp (Exim 3.36 #1 (Debian))
	id 1CPi33-0004HG-00; Thu, 04 Nov 2004 13:53:09 +0000
Subject: Re: MIPS32 / MIPS64 release 2 support in simulator
From: David Ung <davidu@mips.com>
To: cgd@broadcom.com
Cc: gdb-patches@sources.redhat.com, nigel@mips.com
In-Reply-To: <yov5d5yuojo4.fsf@xl-sj1-01.sj.broadcom.com>
References: <1099495559.2778.53.camel@stockwell.mips.com>
	 <mailpost.1099495587.2562@news-sj1-1>
	 <yov5zn1yzx90.fsf@ldt-sj3-010.sj.broadcom.com>
	 <mailpost.1099501062.5136@news-sj1-1>
	 <yov5d5yuojo4.fsf@xl-sj1-01.sj.broadcom.com>
Content-Type: text/plain
Organization: MIPS Technologies UK
Message-Id: <1099576389.2778.90.camel@stockwell.mips.com>
Mime-Version: 1.0
Date: Thu, 04 Nov 2004 13:53:00 -0000
Content-Transfer-Encoding: 7bit
X-MTUK-Scanner: Found to be clean
X-MTUK-SpamCheck: not spam, SpamAssassin (score=-4.831, required 4, AWL,
	BAYES_00)
X-SW-Source: 2004-11/txt/msg00060.txt.bz2

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.