From: Nick Clifton <nickc@redhat.com>
To: vapier@gentoo.org
Cc: gdb-patches@sourceware.org
Subject: RFA: AArch64 sim
Date: Sun, 28 Jun 2015 12:25:00 -0000 [thread overview]
Message-ID: <87vbe8hvfo.fsf@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2601 bytes --]
Hi Mike,
The attached patch adds an aarch64 simulator to gdb's sim library. It
is based upon the smallaarch64sim project:
http://sourceforge.net/projects/smallaarch64sim/
I converted it to C (from C++) because I prefer coding in C, extended
it so that it could run on non x86 hosts, and added some more
instruction emulations.
This is still a work in progress as it does not yet emulate all the
aarch64 instructions, nor does it have a testsuite. Plus of course
there are bound to be bugs to be fixed. But with this sim in place I
am able to run the gcc and g++ testsuites for an aarch64-elf toolchain
and see results like this:
=== gcc Summary for aarch64-sim ===
# of expected passes 89895
# of unexpected failures 3462
# of expected failures 243
# of unresolved testcases 3
# of unsupported tests 1903
=== gcc Summary for aarch64-sim/-mabi=ilp32 ===
# of expected passes 90026
# of unexpected failures 3276
# of expected failures 242
# of unresolved testcases 4
# of unsupported tests 1936
=== g++ Summary for aarch64-sim ===
# of expected passes 78136
# of unexpected failures 1318
# of expected failures 261
# of unsupported tests 3903
=== g++ Summary for aarch64-sim/-mabi=ilp32 ===
# of expected passes 78608
# of unexpected failures 960
# of unexpected successes 4
# of expected failures 257
# of unsupported tests 3895
So an approximate 96% pass rate for gcc and a 98% pass rate for G++.
Not too bad for a first attempt.
Is this patch OK to apply ?
Cheers
Nick
sim/ChangeLog
2015-06-28 Nick Clifton <nickc@redhat.com>
* configure.tgt (sim_arch): Add aarch64 target.
* configure: Regenerate.
* aarch64: New directory.
* aarch64/aclocal.m4: Generate.
* aarch64/config.in: Generate.
* aarch64/configure: Generate.
* aarch64/configure.ac: New file.
* aarch64/cpustate.c: New file. Models the AArch64 registers.
* aarch64/cpustate.h: New file.
* aarch64/decode.h: Prototypes and types for the decoder
functions.
* aarch64/gdb-if.c: New file. Interface with GDB.
* aarch64/main.c: New file. Stand alone front end for the
simulator.
* aarch64/Makefile.in: New file.
* aarch64/memory.c: New file. Models the AArch64 memory subsystem.
* aarch64/memory.h: New file.
* aarch64/simulator.c: New file. Emulated AArch64 instructions.
* aarch64/simulator.h: New file.
include/gdb/ChangeLog
2015-06-28 Nick Clifton <nickc@redhat.com>
* sim-aarch64.h: New file.
[-- Attachment #2: aarch64.sim.patch.xz --]
[-- Type: application/x-xz, Size: 132012 bytes --]
next reply other threads:[~2015-06-28 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 12:25 Nick Clifton [this message]
2015-07-02 9:17 ` Andre Vieira
2015-07-02 13:53 ` Nicholas Clifton
2015-07-02 14:43 ` Andre Vieira
[not found] ` <55954DEE.50609@arm.com>
2015-07-02 15:20 ` Nicholas Clifton
2015-07-07 17:12 ` Mike Frysinger
2015-07-15 16:58 ` Nick Clifton
2015-07-16 15:19 ` Mike Frysinger
2015-07-17 14:10 ` Nicholas Clifton
2015-11-10 7:32 ` Mike Frysinger
2015-11-19 14:51 ` Nick Clifton
2015-11-20 9:13 ` Mike Frysinger
2015-11-20 10:56 ` Nick Clifton
2015-11-20 19:28 ` Mike Frysinger
2015-11-24 8:50 ` Nick Clifton
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=87vbe8hvfo.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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