From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
Date: Mon, 08 Jun 2020 18:00:05 +0000
Message-ID: <bug-368-13-GonFyaAP0s@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #6)
> Ok, I think I've got something working. In soc/simulator/test_sim.py, I
> replaced the code dealing with my handwritten simulator with what's needed
> to use the pseudocode simulator. All the tests, except for multiplication
> now work
fantastic. now we're cooking. ultimately it should be possible to morph
this into classes that have a "set inputs" method, a "run_program" method,
and a "get results" method.
then we can construct unit tests that can be passed in one class instance
that does qemu, and another that does hardware, another that does simulator,
and compare anything-against-anything.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
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: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 22:31 [libre-riscv-dev] [Bug 368] New: " bugzilla-daemon
2020-06-07 22:34 ` [libre-riscv-dev] [Bug 368] " bugzilla-daemon
2020-06-07 22:39 ` bugzilla-daemon
2020-06-07 22:47 ` bugzilla-daemon
2020-06-07 22:48 ` bugzilla-daemon
2020-06-07 23:02 ` bugzilla-daemon
2020-06-08 17:48 ` bugzilla-daemon
2020-06-08 18:00 ` bugzilla-daemon [this message]
2020-06-08 18:31 ` bugzilla-daemon
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=bug-368-13-GonFyaAP0s@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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