From: Jim Wilson <jimw@sifive.com>
To: joel@rtems.org
Cc: Nick Clifton <nickc@redhat.com>, Simon Marchi <simark@simark.ca>,
gdb@sourceware.org
Subject: Re: Running programs on aarch64 simulator
Date: Mon, 11 May 2020 15:13:42 -0700 [thread overview]
Message-ID: <CAFyWVabKsYMh2x-gS9SFccWaeCQLz50T=EB9n3Fb9eT9gN4nDg@mail.gmail.com> (raw)
In-Reply-To: <CAF9ehCWHRX2WUE5b5sfRzRKMK-QqGegev-J0-smy59Svb_LJ9w@mail.gmail.com>
On Mon, May 11, 2020 at 11:30 AM Joel Sherrill <joel@rtems.org> wrote:
> Thanks Jim. That is very helpful. I managed to get an executable
> to run with aarch64-elf-run and traced it failing quite early at
> newlib-cygwin/libgloss/aarch64/syscalls.c:287 doing something with
> the semi-hosting extensions. Have you seen this simulator work
> well enough recently to run the gcc testsuite?
It has been maybe 2.5 years since I last tried. That is about when I
left Linaro.
> It sounds like for my purposes of where to start development of an
> aarch64 RTEMS port, this is one time we need to skip the gdb simulator
> step. The gdb simulators are just so nice to work through basic issues
> like context switching, stack setup, etc. Since we would only need C
> with basic integer operations and enough FPU support to context
> switch the FPU, 1200 gcc failures may not have been a stopper.
I don't know if any of the system instructions work. A gcc testsuite
run will only test user instructions. I like the gdb simulators too.
That is why I did some work with it.
Jim
next prev parent reply other threads:[~2020-05-11 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:44 Joel Sherrill
2020-05-08 16:09 ` Simon Marchi
2020-05-08 16:57 ` Joel Sherrill
2020-05-08 17:17 ` Simon Marchi
2020-05-11 2:35 ` Simon Marchi
2020-05-11 14:26 ` Nick Clifton
2020-05-11 14:40 ` Joel Sherrill
2020-05-11 17:58 ` Jim Wilson
2020-05-11 18:30 ` Joel Sherrill
2020-05-11 22:13 ` Jim Wilson [this message]
2020-05-08 16:16 ` Luis Machado
2020-05-08 16:44 ` Joel Sherrill
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='CAFyWVabKsYMh2x-gS9SFccWaeCQLz50T=EB9n3Fb9eT9gN4nDg@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=gdb@sourceware.org \
--cc=joel@rtems.org \
--cc=nickc@redhat.com \
--cc=simark@simark.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).