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 335] Formal Correctness Proof for Branch pipeline
Date: Mon, 25 May 2020 00:22:11 +0000
Message-ID: <bug-335-13-asJTjCNHPB@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #10)
> (In reply to Luke Kenneth Casson Leighton from comment #9)
> > hm i feel the need to assert that when the cases are not being enabled,
> > the registers not in use (not changed) should be Asserted 0
> > (self.o.{something}.ok == 0)
> > 
> > this because if they are not zero they will cause a request for a
> > register port write at the MultiCompUnit, which, because their data
> > (self.o.{something}.data) was not initialised, would cause regfile
> > corruption.
> 
> Good idea - done. Caught a bug where a regular branch would write to ctr if
> the branch immediate was just right (or wrong).

these are not fully showing up because we do not have writes to regfile(s) yet.
 if we put together the regfiles and a quick link to the pipelines through the
CompUnits interface, we pretty much have a working CPU done and can catch these
things, because SPRs,  XER, etc will all be spuriously modified.

-- 
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-21 13:04 [libre-riscv-dev] [Bug 335] New: " bugzilla-daemon
2020-05-21 13:05 ` [libre-riscv-dev] [Bug 335] " bugzilla-daemon
2020-05-22 18:24 ` bugzilla-daemon
2020-05-22 18:29 ` bugzilla-daemon
2020-05-22 18:35 ` bugzilla-daemon
2020-05-22 18:42 ` bugzilla-daemon
2020-05-22 18:47 ` bugzilla-daemon
2020-05-22 18:50 ` bugzilla-daemon
2020-05-22 18:50 ` bugzilla-daemon
2020-05-22 19:00 ` bugzilla-daemon
2020-05-24 18:33 ` bugzilla-daemon
2020-05-24 19:20 ` bugzilla-daemon
2020-05-25  0:22 ` 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-335-13-asJTjCNHPB@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