Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bo YU via Gdb <gdb@sourceware.org>
To: gdb@sourceware.org
Cc: sergiodj@redhat.com
Subject: Could we add RISC-V 64-bit (riscv64) buildslave to GDB BuildBot？
Date: Tue, 14 Oct 2025 09:24:59 +0800	[thread overview]
Message-ID: <CAKq8=3KdHN7ES9V5KBVU2TckRX-Uy_AjDvZWfSnC5J4ryvoTcg@mail.gmail.com> (raw)

Hi,

When I was looking at some GDB patches, I was surprised to find that
the GDB buildbot[0] did not support riscv64. Do you know if we have a
plan to add this?

I would be very interested in contributing a riscv64 buildslave to the
project with help of plctlab[1]. I have read the project wiki[2] and
understand that as the contributor, I would be responsible for
maintaining the builder and investigating its issues.

Thanks for your help!

BR,
Bo


[0]: https://sourceware.org/pipermail/gdb-testers/
[1]: https://github.com/plctlab/riscv-lab-access
[2]: https://sourceware.org/gdb/wiki/BuildBot

             reply	other threads:[~2025-10-14  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  1:24 Bo YU via Gdb [this message]
2025-10-14 10:34 ` Mark Wielaard
2025-10-14 15:36   ` Bo YU via Gdb

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='CAKq8=3KdHN7ES9V5KBVU2TckRX-Uy_AjDvZWfSnC5J4ryvoTcg@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=tsu.yubo@gmail.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