From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ipphj-00024y-J5 for qemu-devel@nongnu.org; Wed, 07 Nov 2007 13:32:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ipphj-00024C-6B for qemu-devel@nongnu.org; Wed, 07 Nov 2007 13:32:43 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ipphi-00023x-Vw for qemu-devel@nongnu.org; Wed, 07 Nov 2007 13:32:43 -0500 Received: from sp604001mt.neufgp.fr ([84.96.92.60] helo=Smtp.neuf.fr) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ipphi-0004N7-U8 for qemu-devel@nongnu.org; Wed, 07 Nov 2007 13:32:43 -0500 Received: from [84.102.211.92] by sp604001mt.gpm.neuf.ld (Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006)) with ESMTP id <0JR5008ZXFI10070@sp604001mt.gpm.neuf.ld> for qemu-devel@nongnu.org; Wed, 07 Nov 2007 19:32:29 +0100 (CET) Date: Wed, 07 Nov 2007 19:32:02 +0100 From: Fabrice Bellard Message-id: <473204A2.3030208@bellard.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Subject: [Qemu-devel] Removal of some target CPU macros 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 I noticed that some target CPUs macros have been added while they do not seem necessary. I don't like that because it introduces more #ifdefs which prevent making a version supporting simultaneously all the CPUs. In particular I saw the following: - TARGET_MIPSN32 : it is always combined with TARGET_MIPS64 in target-mips/. If its only usage is to select a different Linux ABI, then I suggest keeping TARGET_MIPS64 and using another define to choose that. - TARGET_PPC64H, TARGET_PPCEMB : I see no reason why they cannot be handled dynamically as the other PowerPC CPU types, provided that TARGET_PPC64 is defined. Is it the long term plan ? Regards, Fabrice.