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 314] Create Condition Register pipeline
Date: Sat, 16 May 2020 18:42:35 +0000
Message-ID: <bug-314-13-3UrSvBOBUT@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-314-13@https.bugs.libre-soc.org/>

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

--- Comment #8 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)

> 
> clueless.  suggest to use nmutil PriorityPicker on FXM (see nmutil) because
> it
> can be used do the one-hot detection very efficiently.
> 
> if the output is not exactly equal to the input from a PriorityPicker
> (and is not zero) then this is the condition for detection that FXM
> is one-hot.
> 
> p = PriorityPicker
> p.i.eq(FXM)
> 
> is_onehot.eq(p.i == p.o & p.i != 0)

For mtocrf I don't think this is necessary. If the onehot condition is not
satisfied, it lists the result as being undefined. This should mean that the
current behavior is acceptable

For mfocrf, the situation is similar, the extra bits of the output register are
undefined, unless the input is onehot, in which case they are set to 0. Setting
them to 0 for all bits not selected by the mask should be acceptable here too

-- 
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: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 15:33 [libre-riscv-dev] [Bug 314] New: " bugzilla-daemon
2020-05-15 15:33 ` [libre-riscv-dev] [Bug 314] " bugzilla-daemon
2020-05-15 15:33 ` bugzilla-daemon
2020-05-15 15:41 ` bugzilla-daemon
2020-05-15 21:53 ` bugzilla-daemon
2020-05-15 22:05 ` bugzilla-daemon
2020-05-16 18:00 ` bugzilla-daemon
2020-05-16 18:27 ` bugzilla-daemon
2020-05-16 18:28 ` bugzilla-daemon
2020-05-16 18:38 ` bugzilla-daemon
2020-05-16 18:38 ` bugzilla-daemon
2020-05-16 18:42 ` bugzilla-daemon [this message]
2020-05-16 18:46 ` bugzilla-daemon
2020-05-16 18:47 ` bugzilla-daemon
2020-05-16 19:30 ` bugzilla-daemon
2020-05-16 20:07 ` bugzilla-daemon
2020-05-16 20:30 ` bugzilla-daemon
2020-05-16 22:06 ` bugzilla-daemon
2020-05-16 22:11 ` bugzilla-daemon
2020-05-16 22:14 ` bugzilla-daemon
2020-05-19 18:08 ` bugzilla-daemon
2020-05-23  1:17 ` [libre-riscv-dev] [Bug 314] Create POWER9 " bugzilla-daemon
2020-05-23  1:21 ` bugzilla-daemon
2020-05-23  1:25 ` bugzilla-daemon
2020-05-23 10:36 ` bugzilla-daemon
2020-05-23 20:30 ` bugzilla-daemon
2020-05-23 21:01 ` bugzilla-daemon
2020-05-24 13:11 ` bugzilla-daemon
2020-05-24 19:57 ` bugzilla-daemon
2020-05-24 20:47 ` 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-314-13-3UrSvBOBUT@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