From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
Date: Thu, 21 May 2020 16:02:24 +0000
Message-ID: <bug-333-13-0mvEcKbSsh@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=333
--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hm need to decide the register allocation scheme. it is ok to have 4bit CR go
into a 32bit operand but not to have CR data go down an INT path.
or, if we do, MUXes are needed to cross data from one series of regfile paths
to another.
this could be done for when we have the cyclic buffers in place, easily.
--
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: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 17:55 [libre-riscv-dev] [Bug 333] New: " bugzilla-daemon
2020-05-20 18:16 ` [libre-riscv-dev] [Bug 333] " bugzilla-daemon
2020-05-20 18:37 ` bugzilla-daemon
2020-05-20 18:45 ` bugzilla-daemon
2020-05-20 18:52 ` bugzilla-daemon
2020-05-20 18:59 ` bugzilla-daemon
2020-05-20 18:59 ` bugzilla-daemon
2020-05-20 19:39 ` bugzilla-daemon
2020-05-20 19:42 ` bugzilla-daemon
2020-05-20 19:46 ` bugzilla-daemon
2020-05-21 2:05 ` bugzilla-daemon
2020-05-21 16:02 ` bugzilla-daemon [this message]
2020-05-21 17:23 ` bugzilla-daemon
2020-05-21 17:32 ` bugzilla-daemon
2020-05-21 17:39 ` bugzilla-daemon
2020-05-21 17:46 ` bugzilla-daemon
2020-05-21 17:50 ` bugzilla-daemon
2020-05-21 18:30 ` bugzilla-daemon
2020-05-21 18:34 ` bugzilla-daemon
2020-05-21 18:35 ` bugzilla-daemon
2020-05-21 18:43 ` bugzilla-daemon
2020-05-21 18:56 ` bugzilla-daemon
2020-05-21 18:59 ` bugzilla-daemon
2020-05-21 19:08 ` bugzilla-daemon
2020-05-21 19:09 ` bugzilla-daemon
2020-05-21 19:22 ` bugzilla-daemon
2020-05-21 19:23 ` bugzilla-daemon
2020-05-21 19:28 ` bugzilla-daemon
2020-05-21 19:37 ` bugzilla-daemon
2020-05-21 19:50 ` bugzilla-daemon
2020-05-21 19:59 ` bugzilla-daemon
2020-05-22 13:36 ` bugzilla-daemon
2020-05-22 13:49 ` bugzilla-daemon
2020-05-24 20:48 ` 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-333-13-0mvEcKbSsh@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