public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: gdb-patches@sourceware.org
Subject: RISC-V GDB Port v3
Date: Mon, 06 Mar 2017 20:31:00 -0000	[thread overview]
Message-ID: <20170307043029.3672-1-palmer@dabbelt.com> (raw)

Sorry it took me so long to get around to all the feedback, I was trying to
finish up grad school so I could start working full time on RISC-V software and
the GDB port fell through the cracks.  This is now part of my job, so hopefully
I'll be able to be better about this in the future.

I've attempted to fix all the outstanding comments with the v2 patch set, but
since it's been a while I'm not 100% sure I got everything.  Here's the
differences I remember since v2:

 * Changes the frame walking code to use riscv-opc.h instead of hard-coded
   constants.

 * Don't call deprecated functions when printing FP registers.

 * Use the sw_breakpoint_from_kind interface.

 * Add a RISC-V XML target description file, but I think it doesn't do anything
   yet.

I think the only thing I know of that's bad is the target XML description file,
which I don't think works yet.  That said, I want to send this patch set out
just so we can all get on the same page.

If I understand correctly, GDB-8 is set to be branched on the 15th so if I can
fix up our port quickly we can still get it in?

Sorry this took so long!

[PATCH 1/2] RISC-V GDB Port
[PATCH 2/2] RISC-V sim Port

             reply	other threads:[~2017-03-06 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 20:31 Palmer Dabbelt [this message]
2017-03-06 20:31 ` [PATCH 1/2] RISC-V GDB Port Palmer Dabbelt
2017-04-04 21:48   ` Yao Qi
2017-04-24 16:12     ` Palmer Dabbelt
2017-04-05  9:22   ` Yao Qi
2017-03-06 20:31 ` [PATCH 2/2] RISC-V sim Port Palmer Dabbelt
2017-03-10 19:38 ` RISC-V GDB Port v3 Palmer Dabbelt
2017-03-21  9:23 ` Yao Qi
2017-03-21 16:04   ` Palmer Dabbelt
2017-04-05  9:30 ` Yao Qi

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=20170307043029.3672-1-palmer@dabbelt.com \
    --to=palmer@dabbelt.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).