<_whitenotifier-5>
[symbiflow-examples] rodrigomelo9 opened issue #126: Question about constraints - https://git.io/Jt5GS
citypw has joined #symbiflow
<_whitenotifier-5>
[symbiflow-arch-defs] the-centry opened issue #2047: Had anyone tried to make it supporting two kinds of iopads ？ - https://git.io/Jt5WQ
<sf-slack4>
(https://github.com/YosysHQ/yosys) install methods (`make` and `sudo make install`) after finding the same commit as the conda package (Yosys 0.9+3710 (git sha1 2116c585). However, I seem to be getting an abc error (ERROR: Assert `cell->parameters.empty()' failed in passes/techmap/abc9_ops.cc:781.) when I attempt to then build the counter test. Is there some flags I should be setting when I attempt to build yosys and the
<sf-slack4>
corresponding plugins before using them with the rest of the toolchain?
<litghost>
You might have run into one of those issues
<sf-slack4>
<kgugala> @arvindsrinivasan you should actually use yosys from https://github.com/symbiflow/yosys (Symbiflow's fork) as it has features required for symbiflow (some are not merged upstream yet)
<sf-slack4>
<kgugala> there might have been a rebase in the mean time
<sf-slack4>
<kgugala> and since this particular commit is a merge commit it may have been removed
<sf-slack4>
<arvindsrinivasan> I’m still encountering the error
<sf-slack4>
<arvindsrinivasan> Despite having switched to using that exact commit from the symbiflow repo
<sf-slack4>
<arvindsrinivasan> ERROR: Assert `cell->parameters.empty()' failed in passes/techmap/abc9_ops.cc:781. Is there something missing from either repo to have this example work?
<sf-slack4>
<kgugala> the examples are built in the CI in examples repo, so everything must be there
<sf-slack4>
<arvindsrinivasan> Is there something specific to how the conda packages are built theN
<sf-slack4>
<arvindsrinivasan> I feel like locally building yosys should still produce something that works
<sf-slack4>
<arvindsrinivasan> From there I found the 2116c585 commit on both the yosysHQ repo and the symbiflow repo and so I used the yosysHQ one first then the symbiflow repo
kraiskil_ has joined #symbiflow
<litghost>
Are you condident that you are actually running the yosys compiled from that version?
<sf-slack4>
<arvindsrinivasan> Yes I’m saying it builds a binary with the following version Yosys 0.9+3710 (git sha1 UNKNOWN, gcc 10.2.0-13ubuntu1 -fPIC -Os
<sf-slack4>
<arvindsrinivasan> Which I confirmed is the binary that is installed systemwide on my path
<litghost>
Why is git sha1 UNKNOWN? It should reflect the hash of the git repo it was built from, for your own sanity
<sf-slack4>
<arvindsrinivasan> Not sure of that, but the only yosys binary in the folder has this `./yosys --version`
<sf-slack4>
<arvindsrinivasan> I did that and I still build a binary (Yosys 0.9+3710 (git sha1 2116c585, clang 11.0.0-2 -fPIC -Os)) that causes an issue ERROR: Assert `cell->parameters.empty()' failed in passes/techmap/abc9_ops.cc:781.
<sf-slack4>
<kgugala> which example do you try to build?
<sf-slack4>
<arvindsrinivasan> counter_test
<sf-slack4>
<arvindsrinivasan> Specifically for the basys3
<sf-slack4>
<arvindsrinivasan> I apologize if this is stupid, but like, given the conda packages are just built versions of the repo with nothing special, I feel like this should be a supported workflow since the versions of yosys and ABC is the exact same
ByteLawd has quit [Remote host closed the connection]
umarcor has quit [Read error: Connection reset by peer]
rj has joined #symbiflow
<Lofty>
Kinda wish I'd got pinged for the ABC9 assert ^^;
<Lofty>
arvindsrinivasen: are you still around?
<Lofty>
arvindsrinivasan even
<sf-slack4>
<arvindsrinivasan> Hi
<sf-slack4>
<arvindsrinivasan> Whats up Lofty
<Lofty>
I'm...de facto ABC9 maintainer at the moment :P
<Lofty>
So asserts in ABC9 are my domain
<Lofty>
I'll open up the code in a bit, but here's my assumption: a cell with parameters is making its way to ABC9, but ABC9 expects monomorphised cells and can't really deal with it here
<sf-slack4>
<arvindsrinivasan> Cool, that sounds good. I guess the issue I’m having is trying to build yosys locally (not even master) but the specific commit conda package uses for the symbiflow-examples, but the issue I”m having is that the example (which works with the conda package and its install of ABC9) doesn’t work with my own built copy
<Lofty>
litghost: did you file a bug for that parser issue?
<litghost>
The parser issue was a long standing whole in the parser that was fixed
<litghost>
Yosys accepted or interped something that was not allowed, but accepted it
<litghost>
This is the localparam scoping fix
<Lofty>
And 'your own built copy' gives the ABC9 assert?
<litghost>
Unrelated
<litghost>
I'm not sure what arvind's running into, I've not seen it locally
<Lofty>
I recently-ish made a change which exposes bugs in ABC9
<sf-slack4>
<arvindsrinivasan> Yes
<Lofty>
But *this particular* bug is new to me
<sf-slack4>
<arvindsrinivasan> So while I agree this potentially could be a my system issue, I can explain the exact process I followed if anyone wants to try to replicate it on their system
<sf-slack4>
<arvindsrinivasan> I then cloned and installed https://github.com/SymbiFlow/yosys, particularly, commit 2116c585810cddb73777b46ea9aad0d6d511d82b by checking it out and then running `make clean` then `make config-gcc` then `make` and finally `sudo make install`
<sf-slack4>
<arvindsrinivasan> Finally I cloned and installed https://github.com/SymbiFlow/yosys-symbiflow-plugins, particularly, commit 40efa517423c54119440733f34dbd4e0eb14f983 by checking it out and then running `make clean` `make plugins` and finally `sudo make install`
<Lofty>
That made it across, though...you mentioned it was ABC9 and there's no mention of it in the log?
<sf-slack4>
<arvindsrinivasan> Sorry if I was mistaken, but is > ERROR: Assert `cell->parameters.empty()' failed in passes/techmap/abc9_ops.cc:781. Not related to ABC9?
<Lofty>
Oh, I misread it because it wrapped across messages
<Lofty>
My apologies.
peddie has left #symbiflow ["User left"]
<Lofty>
Ugh, I'm struggling to find the source of symbiflow_synth
<sf-slack4>
<arvindsrinivasan> I believe that is the tar files that are unzipped in the second stage of installation