Monday, 2019-10-07

*** tpb has joined #symbiflow00:00
*** mzyn22 has joined #symbiflow02:53
*** mzyn22 has left #symbiflow02:56
*** citypw has joined #symbiflow03:07
*** Bertl_zZ is now known as Bertl06:10
*** OmniMancer has joined #symbiflow06:20
*** _whitelogger has quit IRC10:57
*** _whitelogger has joined #symbiflow10:59
*** OmniMancer has quit IRC11:31
*** Bertl is now known as Bertl_oO12:08
*** freemint has quit IRC12:12
*** freemint has joined #symbiflow13:12
*** craigo has quit IRC13:13
*** freemint has quit IRC14:13
*** freeemint has joined #symbiflow14:13
*** lromor[m] has quit IRC14:19
*** xobs has quit IRC14:19
*** synaption[m] has quit IRC14:19
*** mrhat2010[m] has quit IRC14:19
*** hzeller[m] has quit IRC14:19
*** zeigren has quit IRC14:19
*** nrossi has quit IRC14:19
*** galv[m] has quit IRC14:19
*** alexhw[m] has quit IRC14:19
*** alexhw has quit IRC14:33
*** alexhw has joined #symbiflow15:17
*** alexhw has quit IRC15:20
*** citypw has quit IRC16:01
*** Bertl_oO is now known as Bertl16:03
*** nrossi has joined #symbiflow16:33
*** alexhw[m] has joined #symbiflow17:13
*** hzeller[m] has joined #symbiflow17:13
*** zeigren has joined #symbiflow17:13
*** synaption[m] has joined #symbiflow17:13
*** xobs has joined #symbiflow17:13
*** galv[m] has joined #symbiflow17:13
*** lromor[m] has joined #symbiflow17:13
*** mrhat2010[m] has joined #symbiflow17:13
*** freeemint has quit IRC17:35
*** freeemint has joined #symbiflow17:35
litghostmkurc: Can you make a wip/ branch version on https://github.com/SymbiFlow/vtr-verilog-to-routing of https://github.com/verilog-to-routing/vtr-verilog-to-routing/pull/993 ?17:57
tpbTitle: GitHub - SymbiFlow/vtr-verilog-to-routing: SymbiFlow WIP changes for Verilog to Routing -- Open Source CAD Flow for FPGA Research (at github.com)17:57
litghostmkurc: We cannot predict when Kevin or another VTR dev will be able to merge that PR17:58
*** freeemint has quit IRC18:34
sf-slack<mkurc> @litghost Sure, I'll address your review and then create the wip/ branch.19:08
*** freeemint has joined #symbiflow19:19
*** freeemint has quit IRC19:44
*** freeemint has joined #symbiflow19:44
*** freeemint has quit IRC19:55
*** freeemint has joined #symbiflow19:56
*** adjtm_ has joined #symbiflow20:34
*** adjtm has quit IRC20:37
*** Bertl is now known as Bertl_zZ20:45
*** craigo has joined #symbiflow20:55
*** freeemint has quit IRC21:36
hackerfoolitghost: I haven't had time to reproduce the lxml crash yet, but I found this: https://bugs.launchpad.net/lxml/+bug/157038821:52
tpbTitle: Bug #1570388 “Serialisation error when writing a large file (> 2...” : Bugs : lxml (at bugs.launchpad.net)21:52
litghostIf that is the issue, it was reported 3 years ago, and got absolutely no updates21:54
litghostSo :(21:54
litghostHowever it does seem like it has a good chance of matching our issue21:56
litghostI'm trying their replication now to see if it fails in the same way21:57
litghostI'm working on getting usan/asan/etc to run against libxml2/libxslt and see what (if anything) crops up21:58
hackerfoolxml uses libxml2: https://bugzilla.gnome.org/show_bug.cgi?id=79619221:58
tpbTitle: Bug 796192 libxml2, xml file reader issue when file size is greater than 2GB (at bugzilla.gnome.org)21:58
litghosthackerfoo: Yes, which makes finding the bug more "exciting"21:58
litghosthackerfoo: The bug could exist in lxml, libxml2, or be an exciting combination !!!21:59
hackerfooIt could still be in our code, too.22:02
litghostNope!  Because https://bugs.launchpad.net/lxml/+bug/1570388 is exactly our bug22:07
tpbTitle: Bug #1570388 “Serialisation error when writing a large file (> 2...” : Bugs : lxml (at bugs.launchpad.net)22:07
litghostLike exact same symptom and everything22:07
litghostNow it is possible that they (openpyxl) have the same bug we do, but that feels unlikely22:09
hackerfooWell, now we have code to reproduce the bug.22:09
litghostKind of, it's still intermixed with openpyxl, so it is no better per say than what we have22:12
litghostA straight forward large loop didn't replicate22:12
*** freeemint has joined #symbiflow22:17
duck2did we upgrade to a >2.5gb xml file? :D22:21
litghost~3.8 GB :D22:22
*** freeemint has quit IRC22:22
litghostI found the libxml2 bug, and it super stupid22:56
hackerfooWhat was it?23:01
litghostint written ... written += bytes_write_last_call ... if (written < 0) error23:01
litghoste.g. what we expected23:02
litghostlibxml2 is totally misusing int (versus size_t/ssize_t)23:02
hackerfooI wonder if Clang or GCC has a warning for that (casting size_t/ssize_t to int.)23:03
litghosthackerfoo: It does not, but "-fsanitize=undefined" with clang produced:23:06
litghostxmlIO.c:3416:19: runtime error: signed integer overflow: 2147481777 + 4000 cannot be represented in type 'int'23:06
litghoste.g. overflowing written23:06
hackerfooSo can we use the whole 50T now?23:07
duck2oooh23:08
litghostI'm working on a patch, but I believe there was never actually a problem in the output, except that the written counter overflowed23:08
litghostAnd this is why size_t and ssize_t should always be used over int23:09
duck2so it's why it occurs when the file is >2gb23:09
litghostWe suspected it was a 32-bit overflow issue, but the question was where23:09
*** freeemint has joined #symbiflow23:33
*** alainmarcel has joined #symbiflow23:57

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!