From: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, nikunj@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH Risu v3 2/4] configure: Add initial support to PPC64 (big endian)
Date: Thu, 25 May 2017 16:10:21 -0300 [thread overview]
Message-ID: <1495739423-32326-3-git-send-email-joserz@linux.vnet.ibm.com> (raw)
In-Reply-To: <1495739423-32326-1-git-send-email-joserz@linux.vnet.ibm.com>
Uses the same ppc64 source file for both BE/LE archs since they are
essentially the same thing.
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
---
configure | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index 055e6d6..dd64d8b 100755
--- a/configure
+++ b/configure
@@ -51,11 +51,7 @@ guess_arch() {
elif check_define __aarch64__ ; then
ARCH="aarch64"
elif check_define __powerpc64__ ; then
- if check_define __BIG_ENDIAN__; then
- ARCH="ppc64"
- else
- ARCH="ppc64le"
- fi
+ ARCH="ppc64le"
else
echo "This cpu is not supported by risu. Try -h. " >&2
exit 1
@@ -127,6 +123,9 @@ OBJDUMP="${OBJDUMP-${CROSS_PREFIX}objdump}"
if test "x${ARCH}" = "x"; then
guess_arch
+elif test "x${ARCH}" = "xppc64"; then
+ # ppc64 and ppc64le uses the same C source code
+ ARCH="ppc64le"
fi
generate_makefilein
--
2.7.4
next prev parent reply other threads:[~2017-05-25 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 19:10 [Qemu-devel] [PATCH Risu v3 0/4] PPC64 Improvements Jose Ricardo Ziviani
2017-05-25 19:10 ` [Qemu-devel] [PATCH Risu v3 1/4] risugen_ppc64: Load random 128-bit data to vector registers Jose Ricardo Ziviani
2017-05-25 19:10 ` Jose Ricardo Ziviani [this message]
2017-05-25 19:10 ` [Qemu-devel] [PATCH Risu v3 3/4] risugen, risugen_ppc64.pm: Add support ppc64 (big-endian) Jose Ricardo Ziviani
2017-05-25 19:10 ` [Qemu-devel] [PATCH Risu v3 4/4] build: Add support to PowerPC BE and remove ARCH Jose Ricardo Ziviani
2017-05-30 14:27 ` Peter Maydell
2017-05-30 18:55 ` joserz
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=1495739423-32326-3-git-send-email-joserz@linux.vnet.ibm.com \
--to=joserz@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--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).