From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 271] SigDecode in power_fields has extra spurious fields
Date: Mon, 30 Mar 2020 09:06:01 +0000
Message-ID: <bug-271-13-YbUAaJsV8J@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #4)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > what do you think of the idea of adding signals with the same name as
> > the fields?
>
>
> Haven't you already done this with power_fields/power_fieldsn?
if you recall i mentioned this a month ago particularly when we did those
recursive expressions. the distinction between nmigen expressions and nmigen
signals is very important.
they are expressions rather than signals
which, if you recall, results in duplication of those expressions wherever they
are used (hence the massivr graphs ladt month despite the code only being a few
lines long)
if the expressions are used a hundred times then they are copied into the HDL a
hindred times because they are a nmigen AST tree fragment.
as signals, the *signal* would be copied and would show up in the yosys graphs.
--
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: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 14:50 [libre-riscv-dev] [Bug 271] New: " bugzilla-daemon
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 [this message]
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-YbUAaJsV8J@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