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] Priority Encoder for Cesar
Date: Sat, 23 May 2020 15:21:27 +0100
Message-ID: <CAPweEDzgCyOH1nkKKiEP56AW4bK8PGEs=JPh3+6t0VKM8QG5pg@mail.gmail.com> (raw)
In-Reply-To: <48c27a2c-e121-01c0-31e7-85ce29ed9333@gmail.com>
On Sat, May 23, 2020 at 3:13 PM Cesar Strauss <cestrauss@gmail.com> wrote:
>
> Hi Luke,
>
> My assignments are piling up. I think I need a Priority Encoder...
:)
in order:
* (5+6) - this should not take more than 5 minutes to do the code
(commit it straight away, then we can review it together)
a preliminary "proof-of-concept" unit test on the other hand might
take ... mm... 20 minutes?
* (4) - review, but consider it "done".
* (2) - L0CacheBuffer with two ports (not two CompLDSTs... yet) - is a
high priority unit test.
* (3) i can handle that... but only when (2) is done
* (1) after L0CacheBuffer unit test is done i expect this to show us
LDSTCompUnit is ok, but yes, needs more testing... but *after* (2).
> I have a wiki page now. I suppose I should update it with the above
> list, right?
yes, it is what it is for.
> I don't mind about the volume, but I would like to know on what to work
> first.
(5+6) high priority to get you "started".
(2) is the next one.
> I think I will start with 4 (review of code-morph), since it's the
> shortest, OK?
and is not involving code-development. yes, review, but consider it "done".
_______________________________________________
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: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 14:12 Cesar Strauss
2020-05-23 14:21 ` Luke Kenneth Casson Leighton [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='CAPweEDzgCyOH1nkKKiEP56AW4bK8PGEs=JPh3+6t0VKM8QG5pg@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