Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 01jun2020
Date: Mon, 1 Jun 2020 12:03:37 -0700
Message-ID: <0D2F440B-EB45-4B1E-804A-36AB40213914@getmailspring.com> (raw)
In-Reply-To: <CAPweEDyrBgT7ueqHAZva6YuZRpXJrv_xnswFuv9k4nv0R8wTNw@mail.gmail.com>

On Jun 1 2020, at 11:33 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Mon, Jun 1, 2020 at 7:30 PM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> attempts on my own(ish), I can see 'the path forward' to what I should
>> have done. I want to be able to contribute more than I currently am,
>> but, I'm realizing that unfortunately I have to learn to crawl before I
>> can walk then run.
> 
> you're braver than i am.  i can contribute small additions to proofs.

Thanks Luke, being with you on this perilous journey makes it much more
fun :)
 
>> I've started the journey at least, and I learn many
>> new things every day.
> 
> :)
> 
>> Today:
>> 
>> If proof_regfile/Register is done, should I try writing
>> proof_regfile/Regfile? or if Michael is doing this, I volunteer to work
>> on TRAP and/or SYS instructions.
> 
> TRAP, SYS and SPR are a higher priority at the moment.
> 
> l.

Should I work on the #TODOs in fu/trap/main_stage.py? Or is there
another file I should work on instead?

On Jun 1 2020, at 11:54 am, Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> I've got a proof for RegFileArray which shouldn't be too hard to
> modify for RegFile.

Awesome! I'm excited to learn from it!

Cole

_______________________________________________
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: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 10:40 Luke Kenneth Casson Leighton
2020-06-01 16:20 ` Tobias Platen
2020-06-01 18:30   ` Cole Poirier
2020-06-01 18:33     ` Luke Kenneth Casson Leighton
2020-06-01 19:03       ` Cole Poirier [this message]
2020-06-01 19:05         ` Luke Kenneth Casson Leighton
2020-06-02  0:22           ` Cole Poirier
2020-06-02 10:11             ` Luke Kenneth Casson Leighton
2020-06-02 22:48               ` Cole Poirier
2020-06-02 23:03                 ` Luke Kenneth Casson Leighton
2020-06-02 23:05                   ` Cole Poirier
2020-06-01 18:54     ` Michael Nolan
2020-06-01 19:02       ` Luke Kenneth Casson Leighton
2020-06-02  6:17 ` Jacob Lifshay
2020-06-02 10:18   ` 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=0D2F440B-EB45-4B1E-804A-36AB40213914@getmailspring.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