Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 342] formal proof of soc.fu.compunits.FunctionUnitBaseSingle needed
Date: Mon, 25 May 2020 19:09:44 +0000
Message-ID: <bug-342-13-lIIMEAoTTY@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-342-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=342

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
extra little funny things that can be thrown in:

* all of rd.go, rd.req, wr.go, wr.req, and issue: if done_o is LOW then
  absolutely all of those should be LOW as well.

  the reason for the existence of done_o over busy_o is because, sigh,
  if you look closely, you can see that some of the latches are reset
  synchronously (a 1 clock delay).  this means that busy_o actually
  drops immediately on completion, and done_o drops a cycle later.

* when the write phase has started, the rd phase is *definitely* over.
  therefore, if wr.req is non-zero, rd.req and rd.go should *definitely*
  be non-zero.

-- 
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

  parent reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 22:57 [libre-riscv-dev] [Bug 342] New: " bugzilla-daemon
2020-05-23 22:57 ` [libre-riscv-dev] [Bug 342] " bugzilla-daemon
2020-05-23 22:58 ` bugzilla-daemon
2020-05-23 23:17 ` bugzilla-daemon
2020-05-24 18:16 ` bugzilla-daemon
2020-05-24 18:25 ` bugzilla-daemon
2020-05-24 20:29 ` bugzilla-daemon
2020-05-24 20:40 ` bugzilla-daemon
2020-05-25 19:00 ` bugzilla-daemon
2020-05-25 19:09 ` bugzilla-daemon [this message]
2020-05-25 20:56 ` bugzilla-daemon
2020-05-26 17:35 ` bugzilla-daemon
2020-05-26 17:52 ` 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-342-13-lIIMEAoTTY@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