From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 271] New: SigDecode in power_fields has extra spurious fields
Date: Sun, 29 Mar 2020 14:50:32 +0000
Message-ID: <bug-271-13@http.bugs.libre-riscv.org/> (raw)
http://bugs.libre-riscv.org/show_bug.cgi?id=271
Bug ID: 271
Summary: SigDecode in power_fields has extra spurious fields
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
hi michael,
SigDecode has had these added to it:
comb += self.x_s.eq(self.df.FormX.S[0])
comb += self.x_sh.eq(self.df.FormX.SH[0:-1])
comb += self.dq_xs_s.eq(self.df.FormDQ.SX_S[0:-1])
DecodeFields itself is where i was intending to be the canonical location
for adding these kinds of things. if you feel that they should be
added as signals, then we should do them in an automated fashion,
because otherwise, after a hundred instructions are added, SigDecode
will be jammed with almost 200 signal fields... *all of which were added
by hand*.
--
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 reply index
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 14:50 bugzilla-daemon [this message]
2020-03-29 17:54 ` [libre-riscv-dev] [Bug 271] " bugzilla-daemon
2020-03-29 18:11 ` bugzilla-daemon
2020-03-29 20:57 ` bugzilla-daemon
2020-03-29 23:15 ` bugzilla-daemon
2020-03-30 9:06 ` bugzilla-daemon
2020-03-30 13:01 ` bugzilla-daemon
2020-03-30 14:11 ` bugzilla-daemon
2020-03-30 15:09 ` bugzilla-daemon
2020-03-30 16:56 ` bugzilla-daemon
2020-03-30 17:05 ` bugzilla-daemon
2020-03-30 18:03 ` bugzilla-daemon
2020-03-30 18:03 ` 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-271-13@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.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