From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 350] LDSTCompUnit also needs to support zeroing on RA
Date: Mon, 25 May 2020 11:57:49 +0000
Message-ID: <bug-350-13-plsd4xOHus@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-350-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=350
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lkcl@lkcl.net |cestrauss@gmail.com
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
cesar this one likewise needs similar tests to the MultiCompUnit, might even
be able to share the same base classes at some point.
again it needs that "multi-process" simulation model:
* one function doing setup, setting oper_i, issue_i, then monitoring busy_o
before exiting
* another that checks busy_o and, when set, proceeds to monitor a single
bit of rd.req, sets the corresponding bit of rd.go for one cycle, then
monitors busy_o before exiting
* likewise for write requests.
this is exactly the same as needed for MultiCompUnit (up to this point).
the additions obviously are to have extra functions that:
* monitor req_adr_o and set go_adr_i
* monitor req_st_o and set go_st_i
* check the address and the data afterwards
--
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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 0:13 [libre-riscv-dev] [Bug 350] New: " bugzilla-daemon
2020-05-25 0:14 ` [libre-riscv-dev] [Bug 350] " bugzilla-daemon
2020-05-25 0:14 ` bugzilla-daemon
2020-05-25 4:03 ` bugzilla-daemon
2020-05-25 11:46 ` bugzilla-daemon
2020-05-25 11:57 ` bugzilla-daemon [this message]
2020-05-28 10:44 ` 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-350-13-plsd4xOHus@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