[libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Mon Feb 24 11:08:26 GMT 2020


http://bugs.libre-riscv.org/show_bug.cgi?id=178

--- Comment #87 from Jean-Paul.Chaput at lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #86)
> (In reply to Jean-Paul.Chaput from comment #80)
> > (In reply to Luke Kenneth Casson Leighton from comment #78)
> > > yuk! :)
> > > 
> > > i am using yosys as of yesterday, now.  can you do yosys -V and let me know?
> > > 
> > > i can then do binary search compiling different versions, looking for the
> > > commit that fails.  i have ccache installed and a stupidly high resource
> > > laptop.  64GB DDR4 RAM, 8 core i9, 2TB NVMe 2500mbytes/sec muhahaha
> > > 
> > > if you let me know the yosys version you use it sets a lower bound on the
> > > git version to start from.
> > 
> > I did use this one, less than a week ago.
> > 
> > https://github.com/cliffordwolf/yosys/archive/yosys-0.9.tar.gz
> 
> ok that appears to be git tagged:
> 
> commit 1979e0b1f2482dbf0562f5116ab444280a377773
> Author: Clifford Wolf <clifford at clifford.at>
> Date:   Mon Aug 26 10:37:53 2019 +0200
> 
>     Yosys 0.9
>     
>     Signed-off-by: Clifford Wolf <clifford at clifford.at>
> 
> 
> although it is easier to track down / confirm with "yosys -V".  hmmm, i
> don't think it will report the version correctly though if built from a .tgz
> 
> i'll *assume* the git tag yosys-0.9 was where that tarball came from.

Hello Luke,

Yes, that's the right one and, yes when built from a tar.gz it do not
report it's version correctly. I've build both versions.

BUT, I was half wrong about the bug. If I persist to think that the
blif file is incorrect, this was not causing the lvx error.
I'm correcting the Coriolis blif parser to account for the righ one.
Strange thing is that now the P&R always fail, whatever the version.
I must have made something wrong in my previous tests (some cached
file perhaps). Sorry for the wrong lead.

This highlight the fact that we must have a way to confirm that the
P&R design is really the nMigen one, at least by re-simulating it.

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


More information about the libre-riscv-dev mailing list