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 332] Formal correctness proof needed for CR pipeline
Date: Sat, 23 May 2020 13:28:54 +0000
Message-ID: <bug-332-13-RaAUEBrBBM@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> michael could you check this when you have a moment?
> 
> commit 27440addbb83c3c13949246b495b8c474b1c2c90 (HEAD -> master,
> origin/master)
> Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> Date:   Sat May 23 11:58:43 2020 +0100
> 
>     add CR_ISEL formal proof to CR pipeline

I changed it so the proof of isel uses the full CR register. Part of the reason
that proof is written the way it is, is I'd already proven that the CR
operations worked when we were using the old interface where it would always
take in the full CR. I wanted to prove that the new way was exactly equivalent
to the old way, so I kept the old proof machinery that used the full CR
register, and added on a way to translate the new interface to that. I think
it's useful to keep doing it that way, so I modified your isel proof to do the
same thing.

-- 
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: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 16:34 [libre-riscv-dev] [Bug 332] New: " bugzilla-daemon
2020-05-20 16:34 ` [libre-riscv-dev] [Bug 332] " bugzilla-daemon
2020-05-20 16:35 ` bugzilla-daemon
2020-05-20 19:26 ` bugzilla-daemon
2020-05-20 19:27 ` bugzilla-daemon
2020-05-20 19:27 ` bugzilla-daemon
2020-05-20 19:27 ` bugzilla-daemon
2020-05-20 19:28 ` bugzilla-daemon
2020-05-21  0:19 ` bugzilla-daemon
2020-05-21 13:01 ` bugzilla-daemon
2020-05-23 10:59 ` bugzilla-daemon
2020-05-23 13:28 ` bugzilla-daemon [this message]
2020-05-23 13:40 ` bugzilla-daemon
2020-05-23 18:43 ` bugzilla-daemon
2020-05-27 14:09 ` 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-332-13-RaAUEBrBBM@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