From: Laurent Vivier <laurent@vivier.eu>
To: Michael Weiser <michael.weiser@gmx.de>, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH v3 4/7] configure: Add aarch64_be-linux-user target
Date: Thu, 21 Dec 2017 11:01:52 +0100 [thread overview]
Message-ID: <1ccca25d-181e-631d-61d3-510b27d761ea@vivier.eu> (raw)
In-Reply-To: <20171220212308.12614-5-michael.weiser@gmx.de>
Le 20/12/2017 à 22:23, Michael Weiser a écrit :
> Add target aarch64_be-linux-user. This allows a qemu-aarch64_be binary
> to be built that will run big-endian aarch64 binaries.
>
> Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> configure | 5 +++--
> default-configs/aarch64_be-linux-user.mak | 1 +
> 2 files changed, 4 insertions(+), 2 deletions(-)
> create mode 100644 default-configs/aarch64_be-linux-user.mak
>
> diff --git a/configure b/configure
> index 9c8aa5a98b..95d5808be1 100755
> --- a/configure
> +++ b/configure
> @@ -6369,7 +6369,7 @@ target_name=$(echo $target | cut -d '-' -f 1)
> target_bigendian="no"
>
> case "$target_name" in
> - armeb|hppa|lm32|m68k|microblaze|mips|mipsn32|mips64|moxie|or1k|ppc|ppcemb|ppc64|ppc64abi32|s390x|sh4eb|sparc|sparc64|sparc32plus|xtensaeb)
> + armeb|aarch64_be|hppa|lm32|m68k|microblaze|mips|mipsn32|mips64|moxie|or1k|ppc|ppcemb|ppc64|ppc64abi32|s390x|sh4eb|sparc|sparc64|sparc32plus|xtensaeb)
> target_bigendian=yes
> ;;
> esac
> @@ -6424,7 +6424,8 @@ case "$target_name" in
> mttcg="yes"
> gdb_xml_files="arm-core.xml arm-vfp.xml arm-vfp3.xml arm-neon.xml"
> ;;
> - aarch64)
> + aarch64|aarch64_be)
> + TARGET_ARCH=aarch64
> TARGET_BASE_ARCH=arm
> bflt="yes"
> mttcg="yes"
> diff --git a/default-configs/aarch64_be-linux-user.mak b/default-configs/aarch64_be-linux-user.mak
> new file mode 100644
> index 0000000000..a69d9d2e41
> --- /dev/null
> +++ b/default-configs/aarch64_be-linux-user.mak
> @@ -0,0 +1 @@
> +# Default configuration for aarch64_be-linux-user
>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2017-12-21 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 21:23 [Qemu-devel] [PATCH v3 0/7] Add aarch64_be-linux-user target Michael Weiser
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 1/7] linux-user: Add support for big-endian aarch64 Michael Weiser
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 2/7] linux-user: Add separate aarch64_be uname Michael Weiser
2017-12-21 10:02 ` Laurent Vivier
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 3/7] linux-user: Fix endianess of aarch64 signal trampoline Michael Weiser
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 4/7] configure: Add aarch64_be-linux-user target Michael Weiser
2017-12-21 10:01 ` Laurent Vivier [this message]
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 5/7] linux-user: Add aarch64_be magic numbers to qemu-binfmt-conf.sh Michael Weiser
2017-12-21 10:01 ` Laurent Vivier
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 6/7] linux-user: Separate binfmt arm CPU families Michael Weiser
2017-12-21 9:59 ` Laurent Vivier
2017-12-20 21:23 ` [Qemu-devel] [PATCH v3 7/7] linux-user: Activate armeb handler registration Michael Weiser
2017-12-21 9:58 ` Laurent Vivier
2017-12-20 21:52 ` [Qemu-devel] [PATCH v3 0/7] Add aarch64_be-linux-user target no-reply
2018-01-08 12:06 ` Peter Maydell
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=1ccca25d-181e-631d-61d3-510b27d761ea@vivier.eu \
--to=laurent@vivier.eu \
--cc=michael.weiser@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).