From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FvFl1-0004Yf-BE for qemu-devel@nongnu.org; Tue, 27 Jun 2006 11:45:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FvFky-0004UZ-CD for qemu-devel@nongnu.org; Tue, 27 Jun 2006 11:45:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FvFky-0004US-6W for qemu-devel@nongnu.org; Tue, 27 Jun 2006 11:45:40 -0400 Received: from [64.233.182.189] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FvFx6-0001bD-1z for qemu-devel@nongnu.org; Tue, 27 Jun 2006 11:58:12 -0400 Received: by nf-out-0910.google.com with SMTP id c31so1013561nfb for ; Tue, 27 Jun 2006 08:45:38 -0700 (PDT) Message-ID: <44A1529D.1070306@gmail.com> Date: Tue, 27 Jun 2006 17:45:33 +0200 MIME-Version: 1.0 Subject: MIPS instruction set configuration, was: Re: [Qemu-devel] Pending MIPS patches References: <449EB5FA.6070405@gmail.com> <449EBC39.3050701@bellard.org> <449FFEB2.1070305@gmail.com> <44A040DA.2050108@bellard.org> In-Reply-To: <44A040DA.2050108@bellard.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Dirk Behme Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Fabrice Bellard wrote: >>>> 3. [PATCH] Add special MIPS multiply instructions >>>> http://lists.gnu.org/archive/html/qemu-devel/2006-04/msg00375.html >>> >>> Same remark. >> >> These are NEC VR54xx specific extensions to the MIPS instruction set. >> >> They are used if you use GCC's -march=vr5400 option. See >> >> www.necelam.com/docs/files/1375_V2.pdf >> >> as well. > > Can you add some kind of define or dynamic processor definnition in your > patch so that we can keep track of the exact instruction set ? Yes, I will update the patch. Any ideas or proposals from anybody how to do this the best way? Are there already examples from other architectures? I think a define to be able to completely select/unselect it at compile time combined with possibility for dynamic runtime selection would be the best? Regards Dirk