From: Jim Wilson <jimw@sifive.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] sim: riscv: new port
Date: Wed, 3 Feb 2021 15:50:59 -0800 [thread overview]
Message-ID: <CAFyWVaY19Vev712kE-9aW5vTw7ufz7-qBVAs4XYUi2DCSwUusg@mail.gmail.com> (raw)
In-Reply-To: <20210112111842.17223-1-vapier@gentoo.org>
We actually have two RISC-V gdb simulators. The one you originally wrote,
and a cgen simulator that Embecosm wrote. I deferred upstreaming your
simulator in the hope that the cgen simulator might be better, but
unfortunately the cgen simulator has a serious problem that it can't easily
support all architecture variations. This is a problem that will only get
worse as more extensions are added to the architecture. I don't know if
the cgen simulator problems are fixable. So I personally prefer your
simulator. But there are others that would like to see the cgen simulator
go in. I don't think we can add both of them. I don't know how to resolve
that debate. Plus there is the problem that I'm involved in so much stuff
that I can't get anything done anymore. But anyways if there is a vote,
I'm voting for your simulator.
Your simulator wasn't lost. It can be found at
https://github.com/riscv/riscv-binutils-gdb/tree/fsf-gdb-10.1-with-sim
This includes your original port, with some minor improvements from Kito
Cheng and myself, and a number of others. They are listed in the ChangeLog
file. This is known to work with the gcc testsuite, though we primarily
use qemu for simulator testing so it doesn't get tested very often. This
is part of riscv/riscv-gnu-toolchain, and if you do SIM=gdb when building
and testing a toolchain, it will use gdb sim to run the gcc testsuite.
Or if you want to start over with a new simulator that is OK too. We can
fix it to work with the gcc testsuite just like we fixed the old one.
Jim
next prev parent reply other threads:[~2021-02-03 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 11:18 Mike Frysinger via Gdb-patches
2021-01-12 11:18 ` [PATCH 2/2] riscv: enable gdb/sim integration Mike Frysinger via Gdb-patches
2021-02-04 10:45 ` Andrew Burgess
2021-02-03 23:50 ` Jim Wilson [this message]
2021-02-04 2:38 ` [PATCH 1/2] sim: riscv: new port Mike Frysinger via Gdb-patches
2021-02-04 22:56 ` Jim Wilson
2021-02-04 10:52 ` Andrew Burgess
2021-02-04 14:14 ` Andrew Burgess
2021-02-05 0:04 ` Mike Frysinger via Gdb-patches
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=CAFyWVaY19Vev712kE-9aW5vTw7ufz7-qBVAs4XYUi2DCSwUusg@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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