From: John Rigby <john.rigby@linaro.org>
To: qemu-devel@nongnu.org
Cc: 'Peter Maydell <peter.maydell@linaro.org>,
John Rigby <john.rigby@linaro.org>,
Riku Voipio <riku.voipio@iki.fi>, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v3 resend 10/11] ARM: Add aarch64 target to configure
Date: Mon, 13 May 2013 00:57:57 -0600 [thread overview]
Message-ID: <1368428278-29299-11-git-send-email-john.rigby@linaro.org> (raw)
In-Reply-To: <1368428278-29299-1-git-send-email-john.rigby@linaro.org>
From: Alexander Graf <agraf@suse.de>
If we want to compile a target machine type that is AArch64 capable,
we need to add a new 64-bit capable ARM target. Use AArch64 since that
is the official ARM LTD name.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: John Rigby <john.rigby@linaro.org>
---
Changes in v3:
- Arch aarch64 gets its own TARGET_ABI_DIR
configure | 8 ++++++++
linux-user/Makefile.objs | 1 +
2 files changed, 9 insertions(+)
diff --git a/configure b/configure
index 9439f1c..4f5be7a 100755
--- a/configure
+++ b/configure
@@ -4191,6 +4191,14 @@ case "$target_arch2" in
target_nptl="yes"
gdb_xml_files="arm-core.xml arm-vfp.xml arm-vfp3.xml arm-neon.xml"
;;
+ aarch64)
+ TARGET_BASE_ARCH=arm
+ TARGET_ABI_DIR=aarch64
+ bflt="yes"
+ target_nptl="yes"
+ gdb_xml_files="aarch64-core.xml aarch64-fpu.xml"
+ target_long_alignment=8
+ ;;
cris)
target_nptl="yes"
;;
diff --git a/linux-user/Makefile.objs b/linux-user/Makefile.objs
index 5899d72..c8709d6 100644
--- a/linux-user/Makefile.objs
+++ b/linux-user/Makefile.objs
@@ -4,4 +4,5 @@ obj-y = main.o syscall.o strace.o mmap.o signal.o \
obj-$(TARGET_HAS_BFLT) += flatload.o
obj-$(TARGET_I386) += vm86.o
obj-$(TARGET_ARM) += arm/nwfpe/
+obj-$(TARGET_AARCH64) += arm/nwfpe/
obj-$(TARGET_M68K) += m68k-sim.o
--
1.8.2.2
next prev parent reply other threads:[~2013-05-13 6:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 6:57 [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 01/11] ARM: Export cpu_env John Rigby
2013-05-13 9:28 ` Peter Maydell
2013-05-13 10:07 ` Alexander Graf
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 02/11] ARM: Prepare translation for AArch64 code John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 03/11] ARM: Add AArch64 translation stub John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 04/11] AArch64: Add gdb stub John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 05/11] linux-user: Don't treat aarch64 cpu names specially John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 06/11] linux-user: Add syscall handling for AArch64 John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 07/11] linux-user: Fix up AArch64 syscall handlers John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 08/11] linux-user: Add signal handling for AArch64 John Rigby
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 09/11] linux-user: Add AArch64 support John Rigby
2013-05-13 6:57 ` John Rigby [this message]
2013-05-13 6:57 ` [Qemu-devel] [PATCH v3 resend 11/11] linux-user: AArch64 requires at least 3.8.0 John Rigby
2013-05-13 8:54 ` [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set Peter Maydell
2013-05-13 13:40 ` John Rigby
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=1368428278-29299-11-git-send-email-john.rigby@linaro.org \
--to=john.rigby@linaro.org \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--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).