Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Binutils <binutils@sourceware.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/8] Bare-metal core dumps for RISC-V
Date: Mon, 7 Dec 2020 11:57:15 -0800	[thread overview]
Message-ID: <CAFyWVaazbrohq3LrS1GjbLUsqT=9vC+MCVbUJmMj3MzgoLuYWg@mail.gmail.com> (raw)
In-Reply-To: <20201207121056.GE2729@embecosm.com>

On Mon, Dec 7, 2020 at 4:10 AM Andrew Burgess <andrew.burgess@embecosm.com>
wrote:

> I agree that it would be a good idea to document this layout
> somewhere.  Am I correct in thinking that here:
>  https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md
> Is where such things should be documented?
>

Yes, this would be the correct place.

I guess it's probably worth getting the documentation approved before
> merging to GDB in case changes are suggested.
>

This would be nice, but I don't consider this required as a prerequisite,
considering that there has been no demand for gdb related docs as yet,
other than DWARF register numbers.  I'm still waiting for the RVI T&R HSC
to create a committee to own the ABI, so meanwhile the ABI committee is
basically me, though I do usually try to get an opinion from at least one
LLVM developer before I accept patches.  And I Iry to include FreeBSD folks
too when necessary.

FYI The binutils patches are OK now.  I think the only unresolved issue is
the NT_ number to use, and I'm OK with the ascii number, though you may
need to get agreement from others on that.

Jim

  reply	other threads:[~2020-12-07 19:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 17:39 Andrew Burgess
2020-12-02 17:39 ` [PATCH 1/8] gdb/riscv: use a single regset supply function for riscv fbsd & linux Andrew Burgess
2021-01-18 14:15   ` Andrew Burgess
2020-12-02 17:39 ` [PATCH 2/8] bfd/binutils: support for gdb target descriptions in the core file Andrew Burgess
2020-12-02 18:21   ` Luis Machado via Gdb-patches
2020-12-02 22:58     ` Jim Wilson
2020-12-03 12:16       ` Luis Machado via Gdb-patches
     [not found]         ` <20201214115512.GI2945@embecosm.com>
2021-01-11 10:19           ` Andrew Burgess
2021-01-11 13:03             ` Luis Machado via Gdb-patches
2020-12-07 12:48     ` Andrew Burgess
2020-12-02 17:39 ` [PATCH 3/8] gdb: write target description into " Andrew Burgess
2020-12-03 20:36   ` Tom Tromey
2020-12-07 14:38     ` Andrew Burgess
2020-12-02 17:39 ` [PATCH 4/8] bfd/riscv: prepare to handle bare metal core dump creation Andrew Burgess
2020-12-02 23:24   ` Jim Wilson
2020-12-07 14:39     ` Andrew Burgess
2020-12-02 17:39 ` [PATCH 5/8] gdb/riscv: introduce bare metal core dump support Andrew Burgess
2020-12-02 18:12   ` Luis Machado via Gdb-patches
2020-12-07 15:17     ` Andrew Burgess
2020-12-07 15:58       ` Luis Machado via Gdb-patches
2020-12-07 16:58         ` Andrew Burgess
2020-12-07 17:24           ` Luis Machado via Gdb-patches
2020-12-07 18:11             ` Andrew Burgess
2020-12-07 19:00               ` Luis Machado via Gdb-patches
2020-12-07 19:23                 ` Andrew Burgess
2020-12-07 19:39                   ` Luis Machado via Gdb-patches
2020-12-07 19:51                     ` Paul Mathieu via Gdb-patches
2020-12-13 10:13                       ` Fredrik Hederstierna via Gdb-patches
2020-12-02 17:39 ` [PATCH 6/8] bfd/binutils: add support for RISC-V CSRs in core files Andrew Burgess
2020-12-02 23:50   ` Jim Wilson
2020-12-07 15:19     ` Andrew Burgess
2020-12-14 13:37     ` Andrew Burgess
2020-12-02 17:39 ` [PATCH 7/8] gdb/riscv: make riscv target description names global Andrew Burgess
2020-12-02 17:39 ` [PATCH 8/8] gdb/riscv: write CSRs into baremetal core dumps Andrew Burgess
2020-12-02 23:59 ` [PATCH 0/8] Bare-metal core dumps for RISC-V Jim Wilson
2020-12-07 12:10   ` Andrew Burgess
2020-12-07 19:57     ` Jim Wilson [this message]
2020-12-03 20:40 ` 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='CAFyWVaazbrohq3LrS1GjbLUsqT=9vC+MCVbUJmMj3MzgoLuYWg@mail.gmail.com' \
    --to=jimw@sifive.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=binutils@sourceware.org \
    --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