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: Re: [libre-riscv-dev] daily kan-ban update 12jul2020
Date: Mon, 13 Jul 2020 10:58:20 +0100
Message-ID: <CAPweEDzaZeW73rVOfMt_r4CvwKpKLeY-Ft4bMu-y6QyyEOnMfw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD4vW=KQFy7KWF--Pnqvjve59G3mQmP-202SWT9jvp_7Ow@mail.gmail.com>

On Mon, Jul 13, 2020 at 10:51 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Mon, Jul 13, 2020, 02:43 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > On Mon, Jul 13, 2020 at 4:49 AM Jacob Lifshay <programmerjake@gmail.com>
> > wrote:
> > >
> > > I also just proposed adding a API to nmigen to output VCD events. You
> > > can think of them as the VCD file having certain times marked. I think
> > > they would be useful for unit tests since we could output them to the
> > > VCD file when we read all the variables in a unit test.
> >
> > so... this is like... debug log notifications?  (which are missing
> > from nmigen, and it's quite a nuisance).
> >
>
> kinda -- they show up as signals in gtkwave

that's good.  it's close enough.  what would be better (if it's at all
possible):  yield ev1("some additional debug info %d" %
some_runtime_variable)  although just the event (at all) would be
extremely useful.

> additional info after 30s of searching:
> https://stackoverflow.com/questions/33095017/how-to-specify-annotations-in-vcd-files

except without nmigen support it's moot.

_______________________________________________
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-07-12 12:43 Luke Kenneth Casson Leighton
2020-07-13  1:48 ` Jacob Lifshay
2020-07-13  3:49   ` Jacob Lifshay
2020-07-13  9:42     ` Luke Kenneth Casson Leighton
2020-07-13  9:51       ` Jacob Lifshay
2020-07-13  9:58         ` 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=CAPweEDzaZeW73rVOfMt_r4CvwKpKLeY-Ft4bMu-y6QyyEOnMfw@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