[libre-riscv-dev] [Bug 329] coriolis2 experiment layout for Dependency Matrices

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Wed Jun 3 23:00:49 BST 2020


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

--- Comment #9 from Jean-Paul.Chaput at lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #8)
> after a little thought, see the diagram in attachment "fu-fu matrix"
> https://bugs.libre-soc.org/attachment.cgi?id=58

Hello Luke,

I'm starting to have automated matrix placement working for the FU-FU
matrix. But the first comparison I can make between matrix placement
and automated placement still got the later winning (by a little).

I have two little remarks about the FU-FU example you gave me:

1. It seems to me that the current example has 4 unit and 3 regs
   (inverted in comment #5).

2. Nothing is connected to gowr3_i, seems strange to me.

I did try to generate a bigger FU-FU, but got stuck here:

Traceback (most recent call last):
  File "fu_fu_matrix.py", line 169, in <module>
    test_fu_fu_matrix()
  File "fu_fu_matrix.py", line 166, in test_fu_fu_matrix
    run_simulation(dut, d_matrix_sim(dut), vcd_name='test_fu_fu_matrix.vcd')
  File "/usr/lib/python3.6/site-packages/nmigen/compat/sim/__init__.py", line
22, in run_simulation
    fragment.domains += ClockDomain("sync")
AttributeError: 'FUFUDepMatrix' object has no attribute 'domains'

I should have the latest nmigen, soc & nmutil repositry versions.

Would it be possible for you to generate a FU-FU matrix as close as possible
to the one intended in terms of number of FU and registers (the idea is to
have a representative amount of wires and gates).

Best regards,

PS1: I use the approach of "not getting to the bottom of things but start like
     a copying monkey", but always still felt a little bit like cheating. Now,
I will
     do it proudly...

PS2: Maybe you have seen this... (personally, I'm at 110 characters)
    
https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-80-Col

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the libre-riscv-dev mailing list