From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 09jul2020
Date: Fri, 10 Jul 2020 18:25:40 +0100
Message-ID: <CAPweEDw=tb4pjUTkcdfWuNFc1Qpoc_B6jiVxkUVbQ+v29ikJhg@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD53q-mmBUcGR-fH+vpiztfe18Cv7s15qO8wcfp60_Z+ng@mail.gmail.com>
On Friday, July 10, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> yes, I know and expected that. I'll repeat myself until you get that I was
> looking at the ra and rb *inputs* in *this stage* as well as the previous
> stage. those *inputs at the beginning of the pipeline* were zero.
ok am with you. that's very odd, because when i added those lines the
correct expected values propagated down the whole thing.
sorry had to narrow down by being able to say what it wasn't :)
there is actually a word for this in vedic epistemology (advaita vedanta)
which is "knowledge by difference". the discrepancy in a comparison *is*
new knowledge.
took a couple of rounds to get there though :)
>
>
> plus, given that the break in the pipeline has been
> > identified i don't believe it necessary to raise the bugreport.
> >
>
> it *is* necessary to report (unless fixed meanwhile), since you got
> distracted by the wrong thing and completely missed that the signals that
> shouldn't have been zero since they *are* connected to the pipeline inputs
> -- those signals *are* zero in the vcd file.
yes with you now. sorry took a while.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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
[not found] <CAPweEDx7hh_eia79gvefVq2J13rbvyAum-5jxr-XX+9SHFG6CQ@mail.gmail.com>
[not found] ` <CAC2bXD55UhNWrqsAQCKczTd=7oSWWrpDSrvLmvHeu77ZZ8mJVQ@mail.gmail.com>
[not found] ` <CAPweEDyJ7ZZFim9vk3YK1ttdARnfqeWqtdV_FeDJ-sfcSW4CTg@mail.gmail.com>
[not found] ` <CAC2bXD4OSaJ7VR0QaqkHJnTR2b5hvuy-o_jcs7DSWAgPPi906A@mail.gmail.com>
[not found] ` <CAPweEDy0R6vXm=Lm166dvNf39h4pnbT-ZdnOtDEu8H1+Vmzs9Q@mail.gmail.com>
[not found] ` <CAC2bXD7yK_pJkNTicyOV3jhwR-Wv+yQFw49sKqeBifR1tYC4-Q@mail.gmail.com>
2020-07-10 12:33 ` Luke Kenneth Casson Leighton
2020-07-10 17:13 ` Jacob Lifshay
2020-07-10 17:25 ` Luke Kenneth Casson Leighton [this message]
2020-07-10 17:59 ` Jacob Lifshay
2020-07-10 20:44 ` Luke Kenneth Casson Leighton
2020-07-10 21:13 ` Jacob Lifshay
2020-07-11 0:46 ` [libre-riscv-dev] bisecting nmigen Jacob Lifshay
2020-07-11 1:12 ` Luke Kenneth Casson Leighton
2020-07-11 3:04 ` Jacob Lifshay
2020-07-11 8:58 ` Luke Kenneth Casson Leighton
2020-07-11 11:34 ` Luke Kenneth Casson Leighton
2020-07-13 1:14 ` Jacob Lifshay
2020-07-13 9:43 ` Luke Kenneth Casson Leighton
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='CAPweEDw=tb4pjUTkcdfWuNFc1Qpoc_B6jiVxkUVbQ+v29ikJhg@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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