From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MM47k-00007r-Ar for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:01:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MM47f-000051-RQ for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:01:36 -0400 Received: from [199.232.76.173] (port=50765 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MM47f-00004q-Mt for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:01:31 -0400 Received: from mail-fx0-f211.google.com ([209.85.220.211]:53761) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MM47f-0004mT-7e for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:01:31 -0400 Received: by fxm7 with SMTP id 7so926274fxm.34 for ; Wed, 01 Jul 2009 11:01:29 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <3d7905b5538d8d8787c8de4ae0486b849063e4cd.1246466962.git.quintela@redhat.com> References: <3d7905b5538d8d8787c8de4ae0486b849063e4cd.1246466962.git.quintela@redhat.com> Date: Wed, 1 Jul 2009 21:01:29 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH 09/13] TARGET_ARCH2 is already known at configure time and it is called target_cpu Remove re-construction in Makefile.target From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "quintela@redhat.com" Cc: qemu-devel@nongnu.org On 7/1/09, quintela@redhat.com wrote: > From: Juan Quintela > TARGET_CPU would be a misleading name. TARGET_ARCH2 means that it's a kind of subarchitecture. TARGET_SUBARCH or TARGET_ABI32_NAME should be OK too. For example, there is no CPU type (or even class of CPUs) called sparc32plus. There is Sparc (a.k.a. Sparc32, V8) and Sparc64 (a.k.a. Ultrasparc, V9, V9plusa etc.). Sparc32plus is a userland mode for Sparc64 CPUs where the address space is limited to 32 bits. The same probably applies to other 32 bit subarchitectures.