Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] daily kan-ban update 21may2020
Date: Thu, 21 May 2020 14:42:45 +0100
Message-ID: <CAPweEDzB_kCw2ugMzJH4WE7sLTb6keYo1ymYQBAZAKTBKvBAuQ@mail.gmail.com> (raw)

yesterday:

* tracking cole and michael's pipeline work.  kept up with bugtracking.
* did the planned CompUnitRecord which begins a Comp Unit API
* added "register specifications" to all the pipeline Input/Output
data structures
* got annoyed at saying "no" to Jacob about a monorepo.  as in: i was annoyed
  *that* i had to say "no".  i don't like it: i'd rather say "yes" to
at least something.
* continued a long-running discussion on comp.arch about a term that is
  entirely missing from Computer Science.  "Phase-aware Function Unit"
  seems to cover it.  took several *days* to establish.
* attended the OpenPOWER-LibreSOC bi-weekly meeting, which highlighted
  a crucial fact that 3.1B UNIX Platform spec currently requires SIMD, and thus
  excludes both LibreSOC and microwatt.  also defined some interfaces (thanks
  to Tim).
* contacted an associate who will be able to explain things to Marketnext about
  the developer install dependencies.
* discussed ideas with Cole about XER and Condition Register fields.

this morni... earlier today:

* created LDSTCompUnitRecord (sorry Cesar!) derived from CompUnitRecord
* rearranged the pipeline code slightly / incrementally to create common classes
* put the "register specifications" into the pipelines, ready for auto-creating
  their association with the (multiple) register files.

rest of today:

think.  still trying to work out a suitable structure for how to
connect multiple (completely different) CompUnits up to regfiles.

blockers:

* DIV and MUL pipelines (Jacob)
* TRAP and SYS pipelines (Cole)
* LDSTCompUnit multi-unit testing (actually probably L0CacheBuffer
issue) (Cesar)
* L0CacheBuffer (Jacob)

l.

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

             reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 13:42 Luke Kenneth Casson Leighton [this message]
2020-05-21 13:52 ` Michael Nolan
2020-05-21 15:35   ` Luke Kenneth Casson Leighton
2020-05-21 18:31     ` Tobias Platen
2020-05-21 18:51       ` Luke Kenneth Casson Leighton
2020-05-21 19:09         ` Jacob Lifshay
2020-05-21 19:32           ` Luke Kenneth Casson Leighton
2020-05-21 21:58             ` [libre-riscv-dev] openpower meeting starting shortly Jacob Lifshay
2020-05-21 18:01 ` [libre-riscv-dev] daily kan-ban update 21may2020 Cole Poirier
2020-05-21 18:51   ` 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=CAPweEDzB_kCw2ugMzJH4WE7sLTb6keYo1ymYQBAZAKTBKvBAuQ@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