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 19:50:17 +0000
Message-ID: <bug-333-13-OykG2tV3ry@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 #28 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ehhhm... i don't actually think main_stage.py needs *any* of these.
* registers are identified and passed in according to DecodeCRIn/Out
in combination with regspecs
* fn_unit might be a good idea to leave in
* insn_type is pretty much literally the only thing that's actually
used, isn't it?
there's nothing in CR main_stage.py which is different for 32/64 bit, is there?
read_cr_whole and write_cr_whole might be useful information if we decide
to do MUXing, but that would be back at the CRCompUnit
do we need input_cr or output_cr - i mean in main_stage.py? i don't
think we do.
class CompCROpSubset(Record):
def __init__(self, name=None):
layout = (('insn_type', InternalOp),
('fn_unit', Function),
('input_cr', CRInSel),
('output_cr', CROutSel),
('read_cr_whole', 1),
('write_cr_whole', 1),
('is_32bit', 1),
)
--
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
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 [this message]
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-OykG2tV3ry@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