From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 08jun2020
Date: Mon, 8 Jun 2020 15:29:17 -0700
Message-ID: <6D991D2F-D9CF-4780-9660-223623481849@gmail.com> (raw)
In-Reply-To: <CAPweEDw1B0+9E7+Z8haPKQ7ejk1eV-m8dRdxG8dFi3p_GLKCpw@mail.gmail.com>
> On Jun 8, 2020, at 3:13 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yyeah. last time i explained it to someone (in detail) it was to
> Alain. it took six hours.
>
> the summary: rather than have dozens of instructions ADD x1, x10 ADD
> x2, x11 ADD x3, x12, instead you deploy SimpleV - with *one*
> instruction - telling it (by setting VL) exactly how many registers,
> in sequence, you would like that *ONE* instruction to push into the
> instruction queue.
>
> that's basically all there is to it. it should be pretty obvious
> therefore that it is effectively a very simple version of an
> instruction "compression algorithm".
>
> in effect, Simple-V is a hardware-level for-loop. if you have heard
> of Zero-Overhead Loops, it is a bit like that. except, whilst ZOHLs
> loop around a *group* of instructions, Simple-V gives the option to
> apply the for-loop to *ANY* instruction, and does so *on* that
> instruction *before* moving on to the next one.
>
> it's like a Sub- Program Counter, in effect
Aha that makes sense! I’ll integrate this into the rest of the insights from the list earlier today.
>
>> Can I ask you to see if you're able to answer some of these questions
>> today, if your illness permits?
>
> it's fine, now: i took... i won't go into the medical details, there's
> a procedure i follow which clears out toxins and it was effective.
> also, a drink made from large quantities of ginger root, cardamons,
> black pepper and chilis, caused me to cough and splutter and generally
> hawk and spit profusely (as might be expected), and surpriise! i'm
> feeling much better.
>
> l.
I’m glad to hear you’re feeling better! However you’ve figured out how to make it happen. Thanks Luke, I’ll hopefully have something for you in about an hour.
Cole
_______________________________________________
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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 20:08 Luke Kenneth Casson Leighton
2020-06-08 21:17 ` Cole Poirier
2020-06-08 22:13 ` Luke Kenneth Casson Leighton
2020-06-08 22:29 ` Cole Poirier [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=6D991D2F-D9CF-4780-9660-223623481849@gmail.com \
--to=colepoirier@gmail.com \
--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