From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gdb-patches@sourceware.org, Palmer Dabbelt <palmer@sifive.com>,
John Baldwin <jhb@freebsd.org>
Subject: Re: [RFC] gdb/riscv: Add target description support
Date: Tue, 13 Nov 2018 15:05:00 -0000 [thread overview]
Message-ID: <20181113150455.GK16539@embecosm.com> (raw)
In-Reply-To: <CAFyWVaa05fi5xYhTMacUidyyj8+gJSzZhK0uLPj+nOF2gqXoGA@mail.gmail.com>
* Jim Wilson <jimw@sifive.com> [2018-11-08 13:57:10 -0800]:
> On Thu, Nov 8, 2018 at 8:07 AM Andrew Burgess
> <andrew.burgess@embecosm.com> wrote:
> > riscv*-*-linux*)
> > # Target: Linux/RISC-V
> > - gdb_target_obs="riscv-linux-tdep.o riscv-tdep.o glibc-tdep.o \
> > + gdb_target_obs="riscv-linux-tdep.oglibc-tdep.o \
> > linux-tdep.o solib-svr4.o symfile-mem.o linux-record.o"
>
> There is a typo here, a space is missing between riscv-linux-tdep.o
> and glibc-tdep.o.
Good spot. I'll fix this.
>
> Otherwise this looks great. I tested it on riscv64-linux and saw no
> new problems. I also tested with riscv-tests/debug against openocd,
> and almost everything that failed before is now passing. There are
> two tests that fail because riscv-tests/debug doesn't know how to
> parse the new {float...double...} string output for FP registers.
> There are two tests that fail for a 32-bit target with
> (gdb) p/x fox = "This little piggy went to the market."
> p/x fox = "This little piggy went to the market."^M
> /scratch/jimw/openocd/fsf-gdb/riscv-gnu-toolchain/build/../riscv-gdb/gdb/regcac\
> he.c:298: internal-error: void
> regcache::restore(readonly_detached_regcache*): \
> Assertion `src != NULL' failed.^M
I have a fix for this issue, but it's not really related to target
register descriptions. I hope to get this posted soon.
> And the same tests fail for a 64-bit target with a timeout. That may
> only be one problem. This should not prevent the XML register set
> support from going in now, and we can worry about debugging these
> problems later. Even with the failures this is a major improvement
> over what we had before.
Great. I just need to review John's feedback and then we can move
this forward.
Thanks again,
Andrew
next prev parent reply other threads:[~2018-11-13 15:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 16:08 Andrew Burgess
2018-11-08 18:33 ` John Baldwin
2018-11-08 19:32 ` Palmer Dabbelt
2018-11-08 19:41 ` John Baldwin
2018-11-14 14:29 ` Andrew Burgess
2018-11-14 17:42 ` John Baldwin
2018-11-08 21:57 ` Jim Wilson
2018-11-13 15:05 ` Andrew Burgess [this message]
2018-11-13 20:08 ` Pedro Alves
2018-11-14 14:58 ` [PATCH] " Andrew Burgess
2018-11-19 3:51 ` Jim Wilson
2018-11-21 11:23 ` Andrew Burgess
2018-11-21 12:37 ` Eli Zaretskii
2018-11-21 13:19 ` Andrew Burgess
2019-02-22 17:42 ` Tom Tromey
2019-02-22 19:24 ` Jim Wilson
2019-02-23 20:51 ` Andrew Burgess
2019-02-24 6:21 ` Jim Wilson
2019-02-26 5:02 ` Joel Brobecker
2019-02-26 17:26 ` Jim Wilson
2019-02-26 18:22 ` Andrew Burgess
2019-02-26 18:40 ` Jim Wilson
2019-02-26 19:27 ` Jim Wilson
2019-02-26 20:30 ` Andrew Burgess
2019-02-23 20:40 ` Andrew Burgess
2019-02-26 11:55 ` Joel Brobecker
2019-03-04 16:18 ` Tom Tromey
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=20181113150455.GK16539@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=jimw@sifive.com \
--cc=palmer@sifive.com \
/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).