From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Jim Wilson <jimw@sifive.com>
Cc: gdb-patches@sourceware.org, Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: [PATCH] RISC-V: Don't decrement pc after break.
Date: Thu, 26 Jul 2018 06:30:00 -0000 [thread overview]
Message-ID: <1475f382-49bb-3b00-b41d-e7470995d3cf@embedded-brains.de> (raw)
In-Reply-To: <CAFyWVabB1PVF8+pejevT=Pxh4mxWieW11X0Fu9y3Xere7=Jk8g@mail.gmail.com>
On 24/07/18 13:41, Jim Wilson wrote:
> On Mon, Jul 23, 2018 at 11:15 PM, Sebastian Huber
> <sebastian.huber@embedded-brains.de> wrote:
>> What is the right place for RISC-V Qemu bug reports?
> You can file an issue in github riscv/riscv-qemu. That is what I
> would do. There is probably also some upstream mailing list or bug
> reporting system but I don't know it.
Just for reference:
https://github.com/riscv/riscv-qemu/issues/156
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2018-07-26 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 0:12 Jim Wilson
2018-07-17 15:37 ` Andrew Burgess
2018-07-23 10:31 ` Sebastian Huber
2018-07-23 15:38 ` Jim Wilson
2018-07-23 17:25 ` Sebastian Huber
2018-07-23 23:27 ` Jim Wilson
2018-07-24 6:15 ` Sebastian Huber
2018-07-24 11:41 ` Jim Wilson
2018-07-26 6:30 ` Sebastian Huber [this message]
2018-08-03 22:05 ` 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=1475f382-49bb-3b00-b41d-e7470995d3cf@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimw@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