From: Peter Maydell <peter.maydell@linaro.org>
To: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH Risu v2 2/3] configure: Add initial support to PPC64 (big endian)
Date: Mon, 13 Mar 2017 12:10:10 +0100 [thread overview]
Message-ID: <CAFEAcA8GPTVg-kUXfTJk17KPaPFAHJ-mGOEXPZLxQ0q9CNRckw@mail.gmail.com> (raw)
In-Reply-To: <1489084718-15294-3-git-send-email-joserz@linux.vnet.ibm.com>
On 9 March 2017 at 19:38, Jose Ricardo Ziviani
<joserz@linux.vnet.ibm.com> wrote:
> This commit set Makefile to point to ppc64le source for both archs
> (ppc64 and ppc64le) because they do the exact same thing. The
> difference is in risugen and how the binary is build.
If we're going to share a single set of source files for ppc64le
and ppc64 (which makes sense) then I think we should use ARCH=ppc64
for that, and rename the 'ppc64le' source files to 'ppc64'.
The rest of these patches look OK.
> 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
>
Incidentally, maybe we should just drop support for
specifying ARCH= manually to configure. I can't really
see a use case where the auto-detection won't do the
right thing.
thanks
-- PMM
next prev parent reply other threads:[~2017-03-13 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 18:38 [Qemu-devel] [PATCH Risu v2 0/3] PPC64 Improvements Jose Ricardo Ziviani
2017-03-09 18:38 ` [Qemu-devel] [PATCH Risu v2 1/3] risugen_ppc64: Load random 128-bit data to VSX registers Jose Ricardo Ziviani
2017-03-09 18:38 ` [Qemu-devel] [PATCH Risu v2 2/3] configure: Add initial support to PPC64 (big endian) Jose Ricardo Ziviani
2017-03-13 11:10 ` Peter Maydell [this message]
2017-03-14 20:22 ` joserz
2017-03-09 18:38 ` [Qemu-devel] [PATCH Risu v2 3/3] risugen, risugen_ppc64.pm: Add support ppc64 (big-endian) Jose Ricardo Ziviani
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=CAFEAcA8GPTVg-kUXfTJk17KPaPFAHJ-mGOEXPZLxQ0q9CNRckw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=joserz@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--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).