<nats`> and in fact it seems the tcl interpreter from vivado is even worse than I thought
<nats`> unsetting vars for example doesn't seem to free memory at all....
<nats`> at least for those I tested get_nodes get_pips get_tiles etc....
<nats`> litghost, I realized something could be broken in my 072 fuzzer !
<nats`> easy to fix
<nats`> if the number of pips is not always a multiple of 64
<litghost> ah
<nats`> the artix works because the numbe rof pips is 64n
<nats`> I wrote a patch I'll test it against artix to verify it works and I would like to test against other target is it possible ?
<nats`> ok I can test with kintex
<nats`> I do it right now
<nats`> litghost, do you have the sha1 of kintex file ?
<litghost> I don't have one handy
<nats`> I fixed it for non integer multiple
<nats`> it doesn't totally optimize you can end with a last block of few index to browse but it shouldn't matter a lot
<mithro> nats`: Do you have to call the gc in some way?
<nats`> nop
<nats`> I simply start new instance of vivado
<nats`> mithro, you don't have the fuzzer 072 built for kintex with file ?
<nats`> real 41m2,012s
<nats`> user 135m58,549s
<nats`> sys 22m59,056s
<nats`> time to build 072 for kintex 70
<nats`> (env) nats@nats-MS-7A72:~/project/symbiflow/prjxray/fuzzers/072-ordered_wires$ sha1sum build/specimen_001/downhill_wires.txt
<nats`> c32830d20ab25241eb560fa3c96302532f5e037a build/specimen_001/downhill_wires.txt
<nats`> (env) nats@nats-MS-7A72:~/project/symbiflow/prjxray/fuzzers/072-ordered_wires$ sha1sum build/specimen_001/uphill_wires.txt
<nats`> 490f19862d57c506a4ed7a945c295d2bcc73fceb build/specimen_001/uphill_wires.txt
<nats`> I'll open a new PR with the fix to be tested
<nats`> is there a lighter way to push a fix than a PR ?
<mithro> nats`: What is so heavy weight about a PR?
<nats`> nothing really heavy but I was wondering when you have to push a small fix of few lines if there are other ways
citypw has joined #symbiflow
<tpb> Title: Fixing Fuzzer 072: supporting all pips count by natsfr · Pull Request #507 · SymbiFlow/prjxray · GitHub (at github.com)
<nats`> if this one is confirmed I'll continue on 074
<nats`> I realized my mistake while working on that one
<nats`> because it has odd num of tiles :D
<nats`> mithro, I restarted a kintex test with the change you told me
<nats`> but I'll go to sleep it's 4am here :D
<nats`> will push that tomorrow
<mithro> nats`: Yes, sounds like a good idea!
_whitelogger has joined #symbiflow
<nats`> good morning
<nats`> finishing to fix the 072 mistake I made it should be good after
<nats`> for a reason I don't understand near the end python only made thread one by one oO
<nats`> real 51m48,687s
<nats`> user 138m34,724s
<nats`> sys 23m25,369s
<nats`> litghost, mithro it should be good now sorry for the mistake :)
Qbix_ has joined #symbiflow
<Qbix_> hi all
<digshadow> hi Qbix_
Rahix has quit [Ping timeout: 258 seconds]
Rahix has joined #symbiflow
Rahix_ has joined #symbiflow
Rahix has quit [Ping timeout: 258 seconds]
_whitelogger has joined #symbiflow
Qbix_ has quit [Ping timeout: 256 seconds]
<nats`> litghost, are you here ? I just came back home and I have question about your change request
Rahix_ has quit [Quit: Rahix_]
<nats`> ping litghost you accepted change but I'm not sure it's good I still doesn't understand what you suggested
<nats`> I just saw the comment oky :)
<nats`> someone could test that fuzzer to have a definitive answer :)
<nats`> I want to know if in all case it generates the same file as former fuzzer
<nats`> I made an other run with the kintex and it took about 39 minutes
<nats`> so maybe at one time because of cpu use the pool was used differently
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow