From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 372] create cycle-accurate JIT-compiler-based processor simulator
Date: Tue, 09 Jun 2020 23:17:05 +0000
Message-ID: <bug-372-13-rAIOYewmBF@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-372-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=372
--- Comment #3 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Jacob Lifshay from comment #0)
> > This could allow simulating our processor model much faster than most other
> > methods.
>
> pearpc already contains both a JIT and a cycle-accurate mode.
> there is also power-gem5 which was recently updated to be capable of
> running a linux kernel (and the 500mb/sec memory leak fixed).
>
> both of these are written in c / c++ and are extremely fast.
>
> is there a compelling reason to, using an appropriate colloquialism,
> "reinvent the wheel?"
I haven't heard of a simulator that is cycle-accurate and JIT-compiled at the
same time, all the ones I've seen before are one or the other (perhaps
dynamically switchable) but not both simultaneously.
This bug report was mostly just to record my idea since it would be useful,
rather than a strict requirement.
This could be used to do things like run a few tens or hundreds of billions of
cycles on a fpga and check that the entire pipeline state matches the simulator
exactly -- unless the simulator is quite fast, that isn't very practical simply
because the existing simulators are too slow or not cycle-accurate.
This is like a bounded-cycle-count formal proof (icr the right term) except
that we can run it for millions or billions of times as many cycles.
--
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
prev parent reply index
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 22:43 [libre-riscv-dev] [Bug 372] New: " bugzilla-daemon
2020-06-09 22:44 ` [libre-riscv-dev] [Bug 372] " bugzilla-daemon
2020-06-09 22:46 ` bugzilla-daemon
2020-06-09 22:53 ` bugzilla-daemon
2020-06-09 23:17 ` bugzilla-daemon [this message]
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-372-13-rAIOYewmBF@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