From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 363] inconsistency between isel and mfcr and crand unit test on bit-ordering of CR
Date: Sun, 07 Jun 2020 20:31:57 +0000
Message-ID: <bug-363-13-7ZwH5Fjk7P@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-363-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=363
--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #9)
> GRR. I believe at some point I used the fields directly generated from
> power_fields.py (fields_x['BF'] or something like that), which needed the
> [0:-1]. But since it got changed to use the signals from the decoder, the
> [0:-1] chopped off the top bit.
ohh... :)
> I think I fixed another error in the decoder
> just like that recently,
i spotted that BFA didn't have [0:-1] on it, which was partly the clue
which led me to try the same on BF.
got there in the end. soc/simple/test/test_core.py now passes and
it runs *all* unit tests. still TODO, the XER checking though
--
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
prev parent reply index
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:51 [libre-riscv-dev] [Bug 363] New: inconsistency between isel and mfcr " bugzilla-daemon
2020-06-04 19:55 ` [libre-riscv-dev] [Bug 363] " bugzilla-daemon
2020-06-04 20:52 ` [libre-riscv-dev] [Bug 363] inconsistency between isel and mfcr and crand " bugzilla-daemon
2020-06-05 3:55 ` bugzilla-daemon
2020-06-05 3:55 ` bugzilla-daemon
2020-06-05 13:39 ` bugzilla-daemon
2020-06-05 13:58 ` bugzilla-daemon
2020-06-05 19:41 ` bugzilla-daemon
2020-06-05 19:47 ` bugzilla-daemon
2020-06-07 20:19 ` bugzilla-daemon
2020-06-07 20:25 ` bugzilla-daemon
2020-06-07 20:31 ` 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-363-13-7ZwH5Fjk7P@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