[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: Running programs on aarch64 simulator
From:       Jim Wilson <jimw () sifive ! com>
Date:       2020-05-11 22:13:42
Message-ID: CAFyWVabKsYMh2x-gS9SFccWaeCQLz50T=EB9n3Fb9eT9gN4nDg () mail ! gmail ! com
[Download RAW message or body]

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
[prev in list] [next in list] [prev in thread] [next in thread]