Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Andrew Waterman <andrew@sifive.com>
To: gdb-patches@sourceware.org
To: amodra@gmail.com
Subject: GDB port for RISC-V
Date: Sat, 22 Oct 2016 23:40:00 -0000	[thread overview]
Message-ID: <1477179592-32501-1-git-send-email-palmer@dabbelt.com> (raw)
In-Reply-To: <1477179037-32066-1-git-send-email-palmer@dabbelt.com>

This message is "In-Reply-To" a larger patch set that contains a whole binutils
port for RISC-V.  During our original patch submission it was suggested we send
the patches relevant to GDB to this mailing list, which is why you might not
have seen the v1 patches.

While there are a few things left to do on our end, I'd like to submit a v2 of
the patch set (the first submission to the GDB mailing list) just so we're all
on the same page.  The exact commit I'm sending is availiable here:

  https://github.com/riscv/riscv-binutils-gdb/commit/a949ca81ca7eca890e27d85d729203253d7862dd

while the whole binutils port, including both the patches submitted to the
binutils mailing list and the autogenerated files necessary for me to build the
RISC-V port, is availiable here:

  https://github.com/riscv/riscv-binutils-gdb/tree/riscv-for-upstream-v2

Aside from review on this mailing list, there are a few problems pointed out by
our first submission that haven't been addresses yet:

 * riscv-opc.h is autogenerated from a Python script.  We will either clean up
   this script enough to be suitable for submission, or will write some CPP
   that produces a similar result.

 * I forgot to fix copyright dates, but I've already made it this far into the
   email...  The plan is to only extend copyrights, and mark every committed
   file as changed in 2016 if it's not already.

Additionally, there are a few issues on our github that are relevant, but I'm
not sure if they block upstreaming:

 * https://github.com/riscv/riscv-gnu-toolchain/issues/124 : "sizeof(long
   double)" is 64-bit on RISC-V, which precludes the use of the Q extension for
   128-bit floating point.  This may cause an ABI-breakage.

 * https://github.com/riscv/riscv-gnu-toolchain/pull/136 : The path for ld.so
   might change.  This would definately be an ABI change.

Thanks to everyone who has provided feedback from the other list, hopefully
this one will be as painless :).

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


       reply	other threads:[~2016-10-22 23:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1477179037-32066-1-git-send-email-palmer@dabbelt.com>
2016-10-22 23:40 ` Palmer Dabbelt [this message]
2016-10-22 23:40   ` [PATCH 1/2] RISC-V GDB Port Palmer Dabbelt
2016-11-03 12:39     ` Yao Qi
2016-11-14 22:39       ` Palmer Dabbelt
2016-11-16 19:36         ` Pedro Alves
2016-11-16 19:40           ` Palmer Dabbelt
2016-11-16 19:48             ` Pedro Alves
2016-11-16 21:40         ` Yao Qi
2016-10-22 23:40   ` [PATCH 2/2] RISC-V GDB Simulator Port Palmer Dabbelt
2016-11-01 20:52   ` GDB port for RISC-V Palmer Dabbelt
2016-11-16 19:17   ` Palmer Dabbelt
2016-11-16 19:17     ` [PATCH 2/3] RISC-V GDB Port Palmer Dabbelt
2016-11-16 19:17     ` [PATCH 3/3] Add a RISC-V GDB NEWS entry Palmer Dabbelt
2016-11-16 19:41       ` Eli Zaretskii
2016-11-16 19:45         ` Palmer Dabbelt
2016-11-16 19:17     ` [PATCH 1/3] RISC-V Sim Port Palmer Dabbelt

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=1477179592-32501-1-git-send-email-palmer@dabbelt.com \
    --to=palmer@dabbelt.com \
    --cc=andrew@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