From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30733 invoked by alias); 3 Nov 2004 19:01:20 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30639 invoked from network); 3 Nov 2004 19:01:18 -0000 Received: from unknown (HELO mms1.broadcom.com) (63.70.210.58) by sourceware.org with SMTP; 3 Nov 2004 19:01:18 -0000 Received: from 63.70.210.1 by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (MMS v5.6.0)); Wed, 03 Nov 2004 11:00:47 -0800 X-Server-Uuid: 97B92932-364A-4474-92D6-5CFE9C59AD14 Received: from mail-sj1-5.sj.broadcom.com (mail-sj1-5.sj.broadcom.com [10.16.128.236]) by mon-irva-10.broadcom.com (8.9.1/8.9.1) with ESMTP id KAA16661; Wed, 3 Nov 2004 10:46:11 -0800 (PST) Received: from xl-sj1-01.sj.broadcom.com (xl-sj1-01 [10.16.129.245]) by mail-sj1-5.sj.broadcom.com (8.12.9/8.12.9/SSF) with ESMTP id iA3Ik4ov020821; Wed, 3 Nov 2004 10:46:04 -0800 (PST) Received: (from cgd@localhost) by xl-sj1-01.sj.broadcom.com ( 8.11.6/8.9.3) id iA3Ik4F01260; Wed, 3 Nov 2004 10:46:04 -0800 X-Authentication-Warning: xl-sj1-01.sj.broadcom.com: cgd set sender to cgd@broadcom.com using -f To: davidu@mips.com cc: gdb-patches@sources.redhat.com Subject: Re: MIPS32 / MIPS64 release 2 support in simulator References: <1099495559.2778.53.camel@stockwell.mips.com> From: cgd@broadcom.com Date: Wed, 03 Nov 2004 19:01:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 X-WSS-ID: 6D97F5300BK624403-98-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00048.txt.bz2 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. chris