From: Blue Swirl <blauwirbel@gmail.com>
To: "quintela@redhat.com" <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
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
Date: Wed, 1 Jul 2009 21:01:29 +0300 [thread overview]
Message-ID: <f43fc5580907011101n1444dfbaj1288a452f3abd981@mail.gmail.com> (raw)
In-Reply-To: <3d7905b5538d8d8787c8de4ae0486b849063e4cd.1246466962.git.quintela@redhat.com>
On 7/1/09, quintela@redhat.com <quintela@redhat.com> wrote:
> From: Juan Quintela <quintela@redhat.com>
>
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.
next prev parent reply other threads:[~2009-07-01 18:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 16:58 [Qemu-devel] [PATCH 00/13] More Build System cleanups quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 01/13] fix XEN Build quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 02/13] fix sparc not solaris build quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 03/13] Remove duplicated definition quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 04/13] use block-nested-y for files inside block/ quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 05/13] use nwfpe-obj-y for consistence quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 06/13] Remove unused Makefile variable quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 07/13] already defined several lines before in block-obj-y quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 08/13] configure already knows what TARGET_BASE_ARCH we need, no need to put the logic in Makefile.target quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 09/13] TARGET_ARCH2 is already known at configure time and it is called target_cpu Remove re-construction " quintela
2009-07-01 18:01 ` Blue Swirl [this message]
2009-07-01 18:21 ` [Qemu-devel] " Juan Quintela
2009-07-01 19:30 ` Stuart Brady
2009-07-01 16:58 ` [Qemu-devel] [PATCH 10/13] chang ifdefs by obj- quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 11/13] configure xen in a single place quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 12/13] configure kvm " quintela
2009-07-01 16:58 ` [Qemu-devel] [PATCH 13/13] configure kqemu " quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580907011101n1444dfbaj1288a452f3abd981@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).