From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3543 invoked by alias); 9 Nov 2004 17:38:10 -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 3512 invoked from network); 9 Nov 2004 17:38:02 -0000 Received: from unknown (HELO mms3.broadcom.com) (63.70.210.38) by sourceware.org with SMTP; 9 Nov 2004 17:38:02 -0000 Received: from 63.70.210.1 by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (MMS v5.6.0)); Tue, 09 Nov 2004 09:37:44 -0800 X-Server-Uuid: 062D48FB-9769-4139-967C-478C67B5F9C9 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 JAA13201; Tue, 9 Nov 2004 09:37:50 -0800 (PST) Received: from xl-sj1-04.sj.broadcom.com (xl-sj1-04 [10.16.129.247]) by mail-sj1-5.sj.broadcom.com (8.12.9/8.12.9/SSF) with ESMTP id iA9Hbhov028036; Tue, 9 Nov 2004 09:37:43 -0800 (PST) Received: (from cgd@localhost) by xl-sj1-04.sj.broadcom.com ( 8.11.6/8.9.3) id iA9HbhA30459; Tue, 9 Nov 2004 09:37:43 -0800 X-Authentication-Warning: xl-sj1-04.sj.broadcom.com: cgd set sender to cgd@broadcom.com using -f To: "Andrew Cagney" cc: "David Ung" , gdb-patches@sources.redhat.com, nigel@mips.com Subject: Re: MIPS32 / MIPS64 release 2 support in simulator References: <1099495559.2778.53.camel@stockwell.mips.com> <1099576389.2778.90.camel@stockwell.mips.com> <418FA243.4060507@gnu.org> <1099937194.2780.151.camel@stockwell.mips.com> <4190EC00.6070501@gnu.org> <4190F770.70006@gnu.org> From: cgd@broadcom.com Date: Tue, 09 Nov 2004 17:38:00 -0000 In-Reply-To: <4190F770.70006@gnu.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 X-WSS-ID: 6D8FDFE21TG1923010-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00165.txt.bz2 At Tue, 09 Nov 2004 11:59:28 -0500, Andrew Cagney wrote: > > Once the legal issues are resolved on your end, will be it be > > acceptable from your POV to merge them all into mips.igen? > > Or do you believe they should always be separate? > > That's a technical question, as I shouldn't, I don't care! actually, i didn't ask that as a technical question. it's a question about the state of the expected copyright/license on mips.igen once the any current issues are resolved. from your response, it sounds like you think that merging everything together would be not-disallowed-by-you. so, mips folks, i think the only solution for now is: (1) mark everything mips32/mips64 in mips.igen with additional mips32r2/mips64r2 markers, but (2) keep the new instructions in a separate file, which i can merge later. chris