From: Cesar Strauss <cestrauss@gmail.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] daily kan-ban update 20jul2020
Date: Mon, 20 Jul 2020 16:14:46 -0300
Message-ID: <1e925e7e-a83f-cf97-75aa-2ab0baf1bf11@gmail.com> (raw)
Yesterday:
* Finished an example of a FSM-based Shifter:
src/soc/experiment/alu_fsm.py
https://bugs.libre-soc.org/show_bug.cgi?id=417
* Started investigating a difference in simulation results between pysim
and cxxsim, with regards to the Shifter example.
It was established that cxxsim probably has a bug.
https://github.com/nmigen/nmigen/issues/439
Today:
* Continue investigating the potential bug in cxxsim.
I think the test case can be simplified by taking out the SHIFT state
and keeping just the handshake states (IDLE and DONE). This would imply,
in turn, that a one bit register should be enough to trigger the problem.
Will add my findings to nMigen #439.
* Fix alu_fsm.py to work in pysim again.
Next:
* Shave an extra cycle from the Shifter, by short-circuiting IDLE and
going straight to SHIFT, when valid_i is already high at DONE. Most
likely, will do it in a new Shifter, to keep this one as simple as possible.
* Thinking about implementing an almost-free exponential speedup, by
shifting by 1,2,4,.. in sequence.
* Simplify my half-finished parallel test case in
src/soc/experiment/test/test_compalu_multi.py, which is too detailed.
Just test for functionality, leave correctness to formal proofs.
* Investigate the possibility to generate useful, structured, commented,
color-formatted gtkw templates in test cases, using the vcd.gtkw module
from pyvcd (which is already a dependency of nMigen).
Cesar
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next reply index
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:14 Cesar Strauss [this message]
2020-07-20 22:05 ` 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=1e925e7e-a83f-cf97-75aa-2ab0baf1bf11@gmail.com \
--to=cestrauss@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