| *** tpb has joined #vtr-dev | 00:00 | |
| *** ZipCPU has joined #vtr-dev | 02:57 | |
| *** ZipCPU has quit IRC | 05:51 | |
| *** ZipCPU has joined #vtr-dev | 06:59 | |
| *** ZipCPU_ has quit IRC | 11:02 | |
| *** ZipCPU_ has joined #vtr-dev | 12:24 | |
| *** ZipCPU has quit IRC | 13:36 | |
| *** ZipCPU has joined #vtr-dev | 13:58 | |
| *** ZipCPU has quit IRC | 15:05 | |
| mithro | Morning everyone! | 15:45 |
|---|---|---|
| mithro | kem_: When I run "./run_reg_test.pl vtr_reg_strong" and something fails, where can I find the failure output? | 16:26 |
| kem_ | mithro: See: https://docs.verilogtorouting.org/en/latest/dev/developing/#debugging-failed-tests | 16:27 |
| kem_ | mithro: and https://docs.verilogtorouting.org/en/latest/vtr/tasks/ | 16:27 |
| mithro | kem_: Thanks! | 16:27 |
| mithro | kem_: What is your thoughts on BOOST? | 16:27 |
| mithro | kem_: Horrible monstrosity - or great proving ground for thing which will become C++ standards? | 16:28 |
| kem_ | mithro: I think BOOST is a great set of libraries | 16:28 |
| kem_ | mithro: But it's also massive and complicated | 16:29 |
| kem_ | mithro: Hence I've tried to avoid adding it as a VTR dependency | 16:29 |
| mithro | kem_: Generally you don't need to pull in the "whole of boost" -- just the library you want? | 16:30 |
| kem_ | mithro: True, but if you want to extract a subset you have to compile it yourself; and boost uses it's own custom build system.... | 16:31 |
| mithro | kem_: I've previously only used the "header only" BOOST libraries | 16:32 |
| mithro | kem_: Do you support windows? | 16:35 |
| mithro | kem_: How did you end up choosing pugixml btw? | 16:37 |
| kem_ | mithro: We kind of unofficially support windows | 16:41 |
| kem_ | mithro: We try to keep the code so that it compile for windows, but thats about it | 16:42 |
| kem_ | mithro: We check that it cross-compiles to windows with mingw-w64 | 16:42 |
| kem_ | mithro: And we did have a regression test which built with cygwin & Visual Studio, but the windows VM seems to have given up so that hasn't been run in the last couple of months | 16:43 |
| kem_ | mithro: As for pugi I basically was looking for a better XML library (we used a very crappy XML parser library, which we became the defacto maintainers for). | 16:44 |
| kem_ | mithro: Best high-level summary I found is: https://stackoverflow.com/questions/9387610/what-xml-parser-should-i-use-in-c | 16:45 |
| tpb | Title: xml parsing - What XML parser should I use in C++? - Stack Overflow (at stackoverflow.com) | 16:45 |
| kem_ | mithro: basically a cleanish API and easily attributable with VTR | 16:46 |
| kem_ | mithro: where why I settled on pugixml | 16:46 |
| kem_ | *distributable with VTR | 16:51 |
| mithro | https://www.irccloud.com/pastebin/620icj8E/ | 16:52 |
| tpb | Title: Snippet | IRCCloud (at www.irccloud.com) | 16:52 |
| mithro | There is something very wrong there -- the error is actually in the .net file..... | 16:53 |
| *** digshadow has joined #vtr-dev | 17:15 | |
| *** vtrbot has quit IRC | 17:45 | |
| *** ZipCPU has joined #vtr-dev | 17:56 | |
| mithro | kem_: This very simple architecture is failing to route.... -> https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/365/files#diff-010a06ab8515072b43b8d6a45261b41c | 19:37 |
| tpb | Title: Support packing when modes provide different routing by mithro · Pull Request #365 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com) | 19:37 |
| *** vtrbot has joined #vtr-dev | 19:51 | |
| *** vtrbot has quit IRC | 19:59 | |
| *** vtrbot has joined #vtr-dev | 20:04 | |
| *** ZipCPU has quit IRC | 21:03 | |
| *** digshadow has quit IRC | 21:07 | |
| mithro | oh | 21:09 |
| mithro | if you put blocks in the corners - things are unhappy | 21:09 |
| *** digshadow has joined #vtr-dev | 21:38 | |
| mithro | Yay! | 21:47 |
| mithro | Test 'vtr_reg_strong' had 0 qor test failures | 21:47 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!