From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 09jun2020
Date: Tue, 9 Jun 2020 14:01:14 -0700
Message-ID: <AB73C9E5-F9FC-4FD7-802E-B04DE2533149@getmailspring.com> (raw)
In-Reply-To: <CAPweEDxcRF8mmQrGBwewE82fuhWq2G4RwrXmJmmcPOjzaWN0CQ@mail.gmail.com>
On Jun 9 2020, at 1:15 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> with michael having added the qemu-execution thing, you should now
> first be able to add a "twi" (or tdi) instruction unit test to that,
> first.
This is filling in the pseudo-code for the soc/decoder/isa/caller.py?
> this will allow you to check that the *simulator* is correct.
How do I use qemu to verify that the simulator is correct? Sorry I've
looked on the bug report and the wiki? Is there a wiki page with the
procedure? If not, what's the procedure I should follow?
> then after you know that the *simulator* is correct, the same unit
> test can be used in test_pipe_caller.py, and in that way you will then
> be able to test that the *hardware* is correct.
Sounds like a plan.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 13:11 Luke Kenneth Casson Leighton
2020-06-09 13:23 ` Tobias Platen
2020-06-09 16:20 ` Luke Kenneth Casson Leighton
2020-06-09 17:21 ` Jacob Lifshay
2020-06-09 17:44 ` Luke Kenneth Casson Leighton
2020-06-09 19:35 ` Cole Poirier
2020-06-09 20:15 ` Luke Kenneth Casson Leighton
2020-06-09 21:01 ` Cole Poirier [this message]
2020-06-09 21:48 ` Luke Kenneth Casson Leighton
2020-06-09 22:07 ` Luke Kenneth Casson Leighton
2020-06-10 0:38 ` Cole Poirier
2020-06-10 13:16 ` Luke Kenneth Casson Leighton
2020-06-10 18:53 ` Michael Nolan
2020-06-10 21:30 ` Cole Poirier
2020-06-09 21:49 Alain D D Williams
2020-06-09 22:48 ` Luke Kenneth Casson Leighton
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=AB73C9E5-F9FC-4FD7-802E-B04DE2533149@getmailspring.com \
--to=colepoirier@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git