From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] configure: Drop armv4l/armv4b distinction in $cpu
Date: Tue, 29 Nov 2011 20:26:55 +0100 [thread overview]
Message-ID: <4ED531FF.50601@suse.de> (raw)
In-Reply-To: <1322587098-12028-1-git-send-email-peter.maydell@linaro.org>
Am 29.11.2011 18:18, schrieb Peter Maydell:
> Drop the distinction between armv4l/armv4b in the $cpu variable
> (ie host cpu type) in favour of calling everything 'arm'. This
> makes it the same as the ARCH setting and removes some special
> casing. The only thing we were using the distinction for was to
> decide which endianness to use in cross compilation; do a cpp
> define check there instead.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> A minor cleanup because I got fed up with saying "armv4b or armv4l".
Nice! Reading "armv4l" on armv7l was pretty confusing at first.
> configure | 26 ++++++++++++--------------
> 1 files changed, 12 insertions(+), 14 deletions(-)
>
> diff --git a/configure b/configure
> index ac4840d..018bf23 100755
> --- a/configure
> +++ b/configure
> @@ -287,10 +287,8 @@ elif check_define __s390__ ; then
> else
> cpu="s390"
> fi
> -elif check_define __ARMEB__ ; then
> - cpu="armv4b"
> -elif check_define __ARMEL__ ; then
> - cpu="armv4l"
> +elif check_define __arm__ ; then
> + cpu="arm"
> elif check_define __hppa__ ; then
> cpu="hppa"
> else
> @@ -307,11 +305,8 @@ case "$cpu" in
> x86_64|amd64)
> cpu="x86_64"
> ;;
> - armv*b)
> - cpu="armv4b"
> - ;;
> - armv*l)
> - cpu="armv4l"
> + armv*b|armv*l|arm)
> + cpu="arm"
> ;;
> hppa|parisc|parisc64)
> cpu="hppa"
> @@ -1243,7 +1238,13 @@ else
>
> # if cross compiling, cannot launch a program, so make a static guess
> case "$cpu" in
> - armv4b|hppa|m68k|mips|mips64|ppc|ppc64|s390|s390x|sparc|sparc64)
> + arm)
> + # ARM can be either way; ask the compiler which one we are
> + if check_define __ARMEB__; then
> + bigendian=yes
> + fi
> + ;;
> + hppa|m68k|mips|mips64|ppc|ppc64|s390|s390x|sparc|sparc64)
> bigendian=yes
> ;;
> esac
> @@ -2871,12 +2872,9 @@ echo "docdir=$docdir" >> $config_host_mak
> echo "confdir=$confdir" >> $config_host_mak
>
> case "$cpu" in
> - i386|x86_64|alpha|cris|hppa|ia64|lm32|m68k|microblaze|mips|mips64|ppc|ppc64|s390|s390x|sparc|sparc64|unicore32)
> + i386|x86_64|alpha|cris|hppa|ia64|lm32|m68k|microblaze|mips|mips64|ppc|ppc64|s390|s390x|sparc|sparc64|unicore32|arm)
If you place "arm" between "alpha" and "cris" instead (alphabetical
order except for i386+x86_64),
Reviewed-by: Andreas Färber <afaerber@suse.de>
Andreas
> ARCH=$cpu
> ;;
> - armv4b|armv4l)
> - ARCH=arm
> - ;;
> *)
> if test "$tcg_interpreter" = "yes" ; then
> echo "Unsupported CPU = $cpu, will use TCG with TCI (experimental)"
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2011-11-29 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 17:18 [Qemu-devel] [PATCH] configure: Drop armv4l/armv4b distinction in $cpu Peter Maydell
2011-11-29 19:26 ` Andreas Färber [this message]
2011-11-29 20:01 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2011-11-30 9:57 Peter Maydell
2011-12-05 20:24 ` andrzej zaborowski
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=4ED531FF.50601@suse.de \
--to=afaerber@suse.de \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).