[libre-riscv-dev] Priority Encoder for Cesar

[libre-riscv-dev] Priority Encoder for Cesar

[Cesar Strauss]

Hi Luke,

My assignments are piling up. I think I need a Priority Encoder...

My tasks, in order of arrival:

1) Fix a bug in the LDSTCompUnit
https://bugs.libre-soc.org/show_bug.cgi?id=318
Status: Luke thinks he fixed it, but needs a review and improving the
unit tests. See: https://bugs.libre-soc.org/show_bug.cgi?id=318#c7

2) Test dual ports (two CompLDSTs with two ports, 4-4 as well) which
write to the same memory
https://bugs.libre-soc.org/show_bug.cgi?id=318#c11
Status: not started

3) Luke tried two LDs in the score6600 code - they failed.
https://bugs.libre-soc.org/show_bug.cgi?id=318#c17
Status: not started, need to check the [prototype] L0CacheBuffer

4) Code-morph LDSTCompUnit to use RecordObject structure, like CompUnitALU
https://bugs.libre-soc.org/show_bug.cgi?id=318#c18
Status: Need a review of Luke's implementation, compared to mine.

5) ALU CompUnit needs to recognise that RA (src1) can be zero
https://bugs.libre-soc.org/show_bug.cgi?id=336
Status: not started

6) Something about the above (5), being optional.
https://bugs.libre-soc.org/show_bug.cgi?id=336#c5
Status: not started

I have a wiki page now. I suppose I should update it with the above
list, right?

I don't mind about the volume, but I would like to know on what to work
first.

I think I will start with 4 (review of code-morph), since it's the
shortest, OK?

Regards,

Cesar

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] Priority Encoder for Cesar

[Luke Kenneth Casson Leighton]

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