From: Michael Nolan <mtnolan2640@gmail.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] 4 Simulators?
Date: Thu, 7 May 2020 13:38:49 -0400
Message-ID: <4a2175ed-6d28-8266-dbda-1a7cd52a02c3@gmail.com> (raw)
In-Reply-To: <EDCC7F2A-1F18-4603-9423-666FCFF4C7FB@gatech.edu>
On 5/7/20 1:33 PM, Yehowshua wrote:
> Hello all - I recently became aware that there a 4 different POWER simulators being worked on?
> This is not a good use of resources given that we have access to a bare-metal Talos II.
>
> We can literally run arbitrary instructions on in remotely - this means a simulator should be low priority given that we have an October deadline.
>
> Yehowshua
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>
I think we do need *a* simulator other than the talos II server. When we
have the core somewhat working, we will want to run a bunch of tests on
it, and check those against a reference. While we can use the Talos as a
reference, running code on it (I assume) will be a somewhat manual
process, not really amenable to unit testing. If we have a simulator
though, we can write (or randomly generate) a bunch of unit tests, and
run them in the simulator and our core and compare the results. So we
will need *a* simulator.
However, I do agree that we don't need 4.
--Michael
_______________________________________________
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: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 17:33 Yehowshua
2020-05-07 17:38 ` Michael Nolan [this message]
2020-05-07 18:23 ` Luke Kenneth Casson Leighton
2020-05-07 18:30 ` Yehowshua
2020-05-07 18:40 ` Jacob Lifshay
2020-05-07 18:41 ` Yehowshua
2020-05-07 18:46 ` Jacob Lifshay
2020-05-07 18:53 ` Luke Kenneth Casson Leighton
2020-05-07 18:54 ` Tobias Platen
2020-05-07 19:02 ` 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=4a2175ed-6d28-8266-dbda-1a7cd52a02c3@gmail.com \
--to=mtnolan2640@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