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: Marie Raymond <marierar@yahoo.com>,
	Libre-RISCV General Development
	<libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 12jun2020
Date: Fri, 12 Jun 2020 09:18:38 -0700
Message-ID: <8C5FCBF1-15B4-4C3F-8187-63303B03CF3B@getmailspring.com> (raw)
In-Reply-To: <CAPweEDwd+TKSpNb1_Ha1n56OLvv8YdFxZhCBK+UAgMM0haytFg@mail.gmail.com>

On Jun 12 2020, at 8:53 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> i believe i did this initially :)
> 
> btw *do* create save files and actually save them regularly.  gtkwave
> has a
> habit of segfaulting, particularly if you use tabs.

Ooof. Thank you for this timely tip, before I've had to experience the
inconvenience of gtkwave segfaulting myself.

> if you do that on code that you have yourself written, and also viewed the
> graphviz diagrams, this cross-association will go faster.
> 
> can i suggest looking at the bperm unit test vcd files, first?

That is an excellent idea. Thank you. I think you suggested it on bug
#325 TRAP pipeline, but I was reading in chronological order and was
working based off of your earlier suggestion in comment #74 "ok. 
suggestion. take alu test_pipe_caller.py and cut out absolutely every
test_* except for one, make sure to pick one with only one assembly
instruction. (or take copy of tpc.py, call it tpc2.py) then run it and
load the generated alu_simulator.gtk in gtkwave." By the way I couldn't
find anything that contained either 'tpc' or 'tpc2' using grep and find.
Will look at bpermd in gtkwave now :)

> my partner marie has a contact at HK University, please do point her
> at it
> when you have it written. (a short wiki page is great).
> 
> we have something on the front page already however it is embedded
> *in* the
> front page and so is not really clear.
> 
> we also cannot call it "jobs" because sigh that implies salaries, per-hour
> payments, employment, that we will cover their insurance costs, holidays
> and so on.  wark-wark.

Appreciated. Created a bug report so that this doesn't get lost in "old
style 'keeping track of things' (an oxymoron) with email".
https://bugs.libre-soc.org/show_bug.cgi?id=379

_______________________________________________
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: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 14:28 Cole Poirier
2020-06-12 15:53 ` Luke Kenneth Casson Leighton
2020-06-12 16:18   ` Cole Poirier [this message]
2020-06-12 16:49     ` Luke Kenneth Casson Leighton
2020-06-12 17:07       ` Cole Poirier
2020-06-12 23:20 ` Jacob Lifshay

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=8C5FCBF1-15B4-4C3F-8187-63303B03CF3B@getmailspring.com \
    --to=colepoirier@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    --cc=marierar@yahoo.com \
    /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