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 01:04:52 +0000
Message-ID: <bug-316-13-RD9qd5ctBo@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 #63 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #59)
> (In reply to Cole Poirier from comment #57)
> > Upon further investigation the import errors appear to be non-trivial to fix
> > so I am leaving them alone
> 
> que? que? give me a hint, i can take a look.

I must stop for today. I don't have confidence that I can write the necessary
code with the level of care necessary at this point at the end of my day, so I
will refrain from doing so and continue tomorrow with integrating Bpermd into
fu/logical. Below is the failed test info that I got when trying to fix import
errors in two of the tests.


Tried to fix the following two tests (stack traces provided for debuggability):
```
Failed test1:
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem2_fu_matrix.py",
line 20, in <module>
    from ..experiment.score6600 import IssueToScoreboard, RegSim, instr_q,
wait_for_busy_clear, wait_for_issue, CompUnitALUs, CompUnitBR, CompUnitsBase
  File "/home/colepoirier/src/soc/src/soc/experiment/score6600.py", line 17, in
<module>
    from soc.experiment.compalu import ComputationUnitNoDelay
  File "/home/colepoirier/src/soc/src/soc/experiment/compalu.py", line 9, in
<module>
    from soc.experiment.alu_hier import CompALUOpSubset
  File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20, in
<module>
    from soc.alu.alu_input_record import CompALUOpSubset
ModuleNotFoundError: No module named 'soc.alu'

Failed test 2:
File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem_fu_matrix.py", line
24, in <module>
    from ..experiment.score6600 import IssueToScoreboard, RegSim, instr_q,
wait_for_busy_clear, wait_for_issue, CompUnitALUs, CompUnitBR
  File "/home/colepoirier/src/soc/src/soc/experiment/score6600.py", line 17, in
<module>
    from soc.experiment.compalu import ComputationUnitNoDelay
  File "/home/colepoirier/src/soc/src/soc/experiment/compalu.py", line 9, in
<module>
    from soc.experiment.alu_hier import CompALUOpSubset
  File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20, in
<module>
    from soc.alu.alu_input_record import CompALUOpSubset
ModuleNotFoundError: No module named 'soc.alu'
```

Fixing the path of soc.alu to be soc.fu.alu results in the tests still failing
but with a different error:

```
Failed test 1:
ERROR: soc.scoreboard.test_mem2_fu_matrix.test_mem_fus
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem2_fu_matrix.py",
line 585, in test_mem_fus
    vcd_name='test_mem_fus.vcd')
  File "/home/colepoirier/src/nmigen/nmigen/compat/sim/__init__.py", line 22,
in run_simulation
    fragment.domains += ClockDomain("sync")
AttributeError: 'MemFunctionUnits' object has no attribute 'domains'

Failed test2:
ERROR: soc.scoreboard.test_mem_fu_matrix.test_mem_fus
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem_fu_matrix.py",
line 679, in test_mem_fus
    vcd_name='test_mem_fus.vcd')
  File "/home/colepoirier/src/nmigen/nmigen/compat/sim/__init__.py", line 22,
in run_simulation
    fragment.domains += ClockDomain("sync")
AttributeError: 'MemFunctionUnits' object has no attribute 'domains'
```

-- 
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
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 [this message]
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-RD9qd5ctBo@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