Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 316] bperm TODO
Date: Wed, 20 May 2020 00:17:38 +0000
Message-ID: <bug-316-13-AOe711XgkR@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=316

--- Comment #53 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #52)
> Michael, or Luke,
> 
> In order to add Bpermd to LogicalMainStage, it appears that I first have to
> add it to soc.decoder.power_enums.InternalOp,

line 102, it is already there.
remember use grep or in-editor search

i also use ctags (aptget install exuberant-ctags)

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/power_enums.py;h=690bf129381cb9ede1d0d92e3564440597fd9e3e;hb=HEAD

so with it already being there, the Case statement can be uncommented and code
added.  try just doing something small and innocuous to confirm that.


regarding code commits, if you make sure there are no syntax errors and second
that no other tests fail you're in the clear.

it is perfectly fine to commit a test that fails although decorating it as such
is generally better.

@unittest.skip("broken") or something if memory serves correctly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 21:01 [libre-riscv-dev] [Bug 316] New: " bugzilla-daemon
2020-05-15 21:06 ` [libre-riscv-dev] [Bug 316] " bugzilla-daemon
2020-05-15 21:11 ` bugzilla-daemon
2020-05-15 21:23 ` bugzilla-daemon
2020-05-15 22:05 ` bugzilla-daemon
2020-05-15 22:14 ` bugzilla-daemon
2020-05-15 22:36 ` bugzilla-daemon
2020-05-16  0:24 ` bugzilla-daemon
2020-05-16  0:50 ` bugzilla-daemon
2020-05-16  1:16 ` bugzilla-daemon
2020-05-16  1:45 ` bugzilla-daemon
2020-05-16  2:03 ` bugzilla-daemon
2020-05-16  3:59 ` bugzilla-daemon
2020-05-16  4:20 ` bugzilla-daemon
2020-05-16  4:35 ` bugzilla-daemon
2020-05-16  4:37 ` bugzilla-daemon
2020-05-16  4:52 ` bugzilla-daemon
2020-05-16 21:15 ` bugzilla-daemon
2020-05-16 21:47 ` bugzilla-daemon
2020-05-16 21:49 ` bugzilla-daemon
2020-05-16 21:52 ` bugzilla-daemon
2020-05-16 22:24 ` bugzilla-daemon
2020-05-16 22:28 ` bugzilla-daemon
2020-05-16 22:36 ` bugzilla-daemon
2020-05-16 22:47 ` bugzilla-daemon
2020-05-16 23:26 ` bugzilla-daemon
2020-05-17 11:09 ` bugzilla-daemon
2020-05-17 17:19 ` bugzilla-daemon
2020-05-17 18:53 ` bugzilla-daemon
2020-05-17 18:56 ` bugzilla-daemon
2020-05-17 21:03 ` bugzilla-daemon
2020-05-17 21:28 ` bugzilla-daemon
2020-05-17 22:19 ` bugzilla-daemon
2020-05-17 23:22 ` bugzilla-daemon
2020-05-17 23:44 ` bugzilla-daemon
2020-05-18  0:14 ` bugzilla-daemon
2020-05-18  0:45 ` bugzilla-daemon
2020-05-18  0:50 ` bugzilla-daemon
2020-05-18  1:23 ` bugzilla-daemon
2020-05-18  4:08 ` bugzilla-daemon
2020-05-18 19:03 ` bugzilla-daemon
2020-05-18 22:29 ` bugzilla-daemon
2020-05-18 22:36 ` bugzilla-daemon
2020-05-18 23:12 ` bugzilla-daemon
2020-05-18 23:17 ` bugzilla-daemon
2020-05-18 23:34 ` bugzilla-daemon
2020-05-18 23:54 ` bugzilla-daemon
2020-05-19  0:05 ` bugzilla-daemon
2020-05-19  0:14 ` bugzilla-daemon
2020-05-19 14:40 ` bugzilla-daemon
2020-05-19 19:16 ` bugzilla-daemon
2020-05-19 19:24 ` bugzilla-daemon
2020-05-19 19:30 ` bugzilla-daemon
2020-05-20  0:09 ` bugzilla-daemon
2020-05-20  0:17 ` bugzilla-daemon [this message]
2020-05-20  0:27 ` bugzilla-daemon
2020-05-20  0:31 ` bugzilla-daemon
2020-05-20  0:40 ` bugzilla-daemon
2020-05-20  0:44 ` bugzilla-daemon
2020-05-20  0:48 ` bugzilla-daemon
2020-05-20  0:50 ` bugzilla-daemon
2020-05-20  0:56 ` bugzilla-daemon
2020-05-20  1:02 ` bugzilla-daemon
2020-05-20  1:04 ` bugzilla-daemon
2020-05-20  1:04 ` bugzilla-daemon
2020-05-20  1:05 ` bugzilla-daemon
2020-05-20  1:07 ` bugzilla-daemon
2020-05-20  1:09 ` bugzilla-daemon
2020-05-20  1:13 ` bugzilla-daemon
2020-05-20  1:34 ` bugzilla-daemon
2020-05-20 17:34 ` bugzilla-daemon
2020-05-20 17:48 ` bugzilla-daemon
2020-05-20 18:07 ` bugzilla-daemon
2020-05-20 18:13 ` bugzilla-daemon
2020-05-20 18:46 ` bugzilla-daemon
2020-05-20 19:42 ` bugzilla-daemon
2020-05-20 19:53 ` bugzilla-daemon
2020-05-20 22:18 ` bugzilla-daemon
2020-05-20 22:20 ` bugzilla-daemon
2020-05-21  0:25 ` bugzilla-daemon
2020-05-21 18:23 ` bugzilla-daemon
2020-05-21 18:38 ` bugzilla-daemon
2020-05-21 18:40 ` bugzilla-daemon
2020-05-21 18:42 ` bugzilla-daemon
2020-05-21 18:44 ` bugzilla-daemon
2020-05-21 19:02 ` bugzilla-daemon
2020-05-21 19:24 ` bugzilla-daemon
2020-05-21 21:36 ` bugzilla-daemon
2020-05-21 21:42 ` bugzilla-daemon
2020-05-21 22:00 ` bugzilla-daemon
2020-05-21 22:16 ` bugzilla-daemon
2020-05-21 22:24 ` bugzilla-daemon
2020-05-22  0:06 ` bugzilla-daemon
2020-05-22  1:20 ` bugzilla-daemon
2020-05-22 18:49 ` bugzilla-daemon
2020-05-23 22:35 ` bugzilla-daemon
2020-05-24 16:45 ` bugzilla-daemon
2020-05-24 17:57 ` bugzilla-daemon
2020-05-24 18:13 ` bugzilla-daemon
2020-05-24 18:26 ` bugzilla-daemon
2020-05-25 21:03 ` bugzilla-daemon
2020-05-25 21:36 ` bugzilla-daemon

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=bug-316-13-AOe711XgkR@https.bugs.libre-soc.org/ \
    --to=bugzilla-daemon@libre-soc.org \
    --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