tweakoz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
OmniMancer has joined #symbiflow
Maya-sama is now known as Miyu
lopsided98 has joined #symbiflow
citypw has quit [Ping timeout: 244 seconds]
OmniMancer has quit [Quit: Leaving.]
Bertl_zZ is now known as Bertl
Vonter has quit [Ping timeout: 268 seconds]
adjtm has quit [Ping timeout: 248 seconds]
<sf-slack2>
<butta> Are others seeing that check rr_graph now takes a very long time with the newest symbiflow-arch-defs? Last week check_rr_graph was taking 5 seconds and its now taking 95 seconds.
<tpb>
Title: cmake: update VTR and add new command line options by acomodi · Pull Request #858 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<sf-slack2>
<acomodi> Try to use this commit 3948971c48cd3ba1f1ba850bd444df48dbc371a8
<sf-slack2>
<butta> @acomodi It's not an issue for us since were commenting out the rr_graph check in source built vpr. Just wondering if it was a known issue.
<duck2>
does it take 95 seconds _with_ suppressed warnings?
<sf-slack2>
<butta> Yes that's with suppressed warnings
<sf-slack2>
<acomodi> @duck2 I was thinking that it might be the cause
<sf-slack2>
<butta> Although I'm writing to a log file on a harddisk, could try dumping to /dev/null
<sf-slack2>
<acomodi> @butta Could you try to launch VPR without the `--suppress_warnings` line?
<duck2>
acomodi: it used to take 140 seconds with the warnings on. I wonder if it's due to printing/logging or due to the execution path being broken so many times.
<sf-slack2>
<butta> @duck2 interesting, with warnings on it only took 5-10 seconds for us
<sf-slack2>
<acomodi> @butta So it's confirmed that `suppress_warnings` is indeed drastically increasing run-time?
proteusguy has quit [Remote host closed the connection]
<duck2>
acomodi: yes i guess. I took another look at http://duck2.lt/warnings.txt and noticed that check_rr_graph completed in normal time when warnings were directed at a log file. 140 seconds was when it was printing to a terminal.
<sf-slack2>
<acomodi> Ok, IMO, being the warning suppression optional, this is not a huge issue
<sf-slack2>
<acomodi> I will check if there is a way to bring warning suppression to acceptable run-time though
<sf-slack2>
<butta> Just ran some tests. Writing log file to our HDD array took 85 seconds to create the device. Writing the log file to a local SSD took 10 seconds to create the device. Printing warning to console took 12 seconds to create device.
<sf-slack2>
<acomodi> @butta Well, that is good news. Thanks for the information. I guess then that if you usually use the HDD instead of the SSD it would be better not to write the suppressed warnings log-file
alexhw has quit [Ping timeout: 245 seconds]
alexhw has joined #symbiflow
acomodi has joined #symbiflow
kraiskil has joined #symbiflow
proteusguy has joined #symbiflow
<litghost>
acomodi: I think it makes sense to make the suppressed warning file optional (e.g. don't write them at all)
<sf-slack2>
<acomodi> litghost: makes sense
kraiskil has quit [Ping timeout: 245 seconds]
<sf-slack2>
<butta> I agree with litghost, we would appreciate having the option to not write to file
acomodi has quit [Quit: Connection closed for inactivity]
tweakoz has joined #symbiflow
Miyu has quit [Ping timeout: 245 seconds]
proteusguy is now known as proteusdude
space_zealot has joined #symbiflow
space_zealot has quit [Ping timeout: 244 seconds]
<mithro>
duck2: How's that rr_graph.xml parser going?
<duck2>
mithro: I'm looking more into updating the schema for arch.xml so that I fully know which features could be needed. There are many features of XSD which can aid in fully validating the file. For instance, segment wire_switches have to correspond to switch names. XSD>1.0 has a <xs:keyref> tag for that. I'll just add comments about these, then let's
<duck2>
see if I'll be able to implement them
<mithro>
duck2: As you come across these ideas, can you log an issue about them?
<duck2>
mithro: ok
<mithro>
duck2: Also need to log those github issues...
<duck2>
mithro: right. I looked at the schemas first so that I can see if we need more features than what is used in the current ones.
<mithro>
duck2: I added some issues to your repository...
<duck2>
mithro: checking them now
alexhw has quit [Remote host closed the connection]