qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH][v2] configure: change endianness test
Date: Wed, 14 Mar 2012 22:24:54 +0100	[thread overview]
Message-ID: <4F610CA6.8030903@weilnetz.de> (raw)
In-Reply-To: <1331757449-20873-1-git-send-email-stuart.yoder@freescale.com>

Am 14.03.2012 21:37, schrieb Stuart Yoder:
> From: Stuart Yoder <stuart.yoder@freescale.com>
>
> Remove the runtime check for endianness, and for platforms
> that can be bit or little endian do a compile time check.
>
> This resolves an issue encountered building QEMU
> under Yocto which was not setting --cross-prefix.
>
> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
> ---
>
> -v2: removed the dynamic runtime test completely,
> added compile time check for mips
>
> configure | 33 ++++++++-------------------------
> 1 files changed, 8 insertions(+), 25 deletions(-)
>
> diff --git a/configure b/configure
> index fe4fc4f..d9c5999 100755
> --- a/configure
> +++ b/configure
> @@ -1269,41 +1269,24 @@ feature_not_found() {
> exit 1;
> }
>
> -if test -z "$cross_prefix" ; then
> -
> -# ---
> -# big/little endian test
> -cat > $TMPC << EOF
> -#include <inttypes.h>
> -int main(int argc, char ** argv){
> - volatile uint32_t i=0x01234567;
> - return (*((uint8_t*)(&i))) == 0x67;
> -}
> -EOF
> -
> -if compile_prog "" "" ; then
> -$TMPE && bigendian="yes"
> -else
> -echo big/little test failed
> -fi
> -
> -else
> -
> -# if cross compiling, cannot launch a program, so make a static guess
> +##########################################
> +# endianness check
> case "$cpu" in
> 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)
> + mips|mips64)
> + if check_define __MIPSEB__; then
> + bigendian=yes
> + fi
> + ;;
> + hppa|m68k|ppc|ppc64|s390|s390x|sparc|sparc64)
> bigendian=yes
> ;;
> esac
>
> -fi
> -
> ##########################################
> # NPTL probe
>

The patch fixes all issues which were addressed in the discussion,
therefore

Reviewed-by: Stefan Weil <sw@weilnetz.de>

Nevertheless the old test which was removed still might be useful
and could be re-added later in a modified form:

Contrary to Paul's argument QEMU does not only support a fixed
set of known host architectures, but also unknown hosts (via TCI).
For those, there remains a small chance that they are big endian
and that they get the wrong endianness now. TCI is still experimental,
so I don't care too much about this small deficit.

Regards,
Stefan W.

  reply	other threads:[~2012-03-14 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 20:37 [Qemu-devel] [PATCH][v2] configure: change endianness test Stuart Yoder
2012-03-14 21:24 ` Stefan Weil [this message]
2012-03-14 21:37   ` Peter Maydell
2012-03-14 21:42     ` Stefan Weil
2012-03-14 21:49   ` Paul Brook

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=4F610CA6.8030903@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aliguori@us.ibm.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stuart.yoder@freescale.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).