Saturday, 2019-01-05

*** tpb has joined #yosys00:00
*** Forty-Bot has quit IRC00:32
*** voxadam has quit IRC01:51
*** voxadam has joined #yosys01:52
*** emeb has left #yosys02:23
*** emeb_mac has joined #yosys02:26
*** wavedrom has quit IRC03:14
*** pie_ has quit IRC04:01
*** pie_ has joined #yosys04:01
*** wavedrom has joined #yosys04:15
*** _whitelogger has quit IRC05:27
*** _whitelogger has joined #yosys05:29
phireWhat's the best way to generate a netlist with proper names on the flipflops?05:31
phireModify the proc_dff (and subsequent passes) to generate and perserve names?05:32
phirewrite some kind of post-processing script or pass that generates a name based on the output wires?05:32
*** pie_ has quit IRC06:13
*** pie_ has joined #yosys06:13
*** emeb_mac has quit IRC06:44
*** _whitelogger has quit IRC06:46
*** _whitelogger has joined #yosys06:59
*** wavedrom has quit IRC07:08
*** rohitksingh has joined #yosys07:28
*** _whitelogger has quit IRC08:12
*** _whitelogger has joined #yosys08:14
daveshahphire: imo, a fix that generated names for cells based on output wire name would be very useful09:18
daveshahs/fix/pass/09:19
*** xerpi has joined #yosys09:37
*** rohitksingh has quit IRC09:58
*** rohitksingh has joined #yosys10:12
*** citypw has joined #yosys10:18
*** Forty-Bot has joined #yosys10:25
*** _whitelogger has quit IRC10:45
*** _whitelogger has joined #yosys10:47
*** fevv8[m] has quit IRC11:03
*** nrossi has quit IRC11:03
*** jfng has quit IRC11:03
*** bluesceada has quit IRC11:06
*** bluesceada has joined #yosys11:10
*** kbeckmann has quit IRC11:11
*** fevv8[m] has joined #yosys11:16
*** nrossi has joined #yosys11:43
*** jfng has joined #yosys11:43
*** citypw has quit IRC11:44
*** citypw has joined #yosys11:46
puddingpimpit seems like it would be useful if there was a traceable link from every AST node to the pass and input AST node(s) that produced it11:55
puddingpimpbut I guess that presumes that the prior AST state is stashed away somewhere11:55
puddingpimpI'm just an observer and not that familiar with yosys internals11:56
phireThe previous state is deleted on each pass11:57
puddingpimpI do know that, I'm part of the way through te yosys manual atm11:58
phirethe src attributes really should be propergated to every single generated node12:02
puddingpimpso there is the HDL AST and then the yosys AST (from what I understand) does the HDL AST from the lexer stick around in memory?12:04
phireWell, you can save out the IL at any point and load it into a new instance of yosys later12:06
puddingpimphow early/late is the AST flattened, eg. if I have 4 instances of a module A, which has two instances of module B, is module A and B optimised once each and then flattened,12:07
puddingpimpor is the whole AST flattened before any later processing12:07
phireI think the typical workflow is to run the hierarchy pass early on before optimising, which I understand flatterns the design.12:13
daveshahread_verilog does by default elaborate & simplify the AST with the default parameter set for a module (turned of with -nodefer); but keeps the AST around in case the module is encountered with a different set of parameters12:14
daveshahhierarchy will elaborate all modules as instantiated with their parameter set12:14
daveshahflattening is optional at this point, and pretty much unrelated to elaboration of the AST12:15
phireOne problem with the manual, is that it doesn't really give you much idea which passes you should be running in which order12:17
daveshahThere is a bit on this in the appnotes at the end12:18
daveshahtldr; always run hierarchy and proc before anything else12:18
phireYeah12:19
phireRight now I'm trying to generate nice looking schematics of my design12:19
daveshahHave you seen https://github.com/nturley/netlistsvg?12:20
tpbTitle: GitHub - nturley/netlistsvg: draws an SVG schematic from a JSON netlist (at github.com)12:20
phireyeah, I'm considering improving it12:20
*** proteusguy has joined #yosys12:23
phireI think I actually want a "looks good in schematic form" technology library.12:24
*** leviathanch has joined #yosys12:29
*** rohitksingh has quit IRC12:47
*** rohitksingh has joined #yosys13:10
*** xerpi has quit IRC13:24
*** xerpi has joined #yosys13:25
*** xerpi has quit IRC13:28
*** rohitksingh has quit IRC14:09
*** rohitksingh has joined #yosys14:43
*** kuldeep has joined #yosys14:45
*** kuldeep_ has joined #yosys14:52
*** kuldeep has quit IRC14:52
*** kuldeep_ is now known as kuldeep14:53
*** emeb_mac has joined #yosys15:24
*** celadon has quit IRC15:29
*** kuldeep_ has joined #yosys15:52
*** kuldeep has quit IRC16:04
*** kuldeep_ has quit IRC16:05
*** kuldeep has joined #yosys16:12
*** lutsabound has joined #yosys16:16
*** proteusguy has quit IRC17:08
*** rohitksingh has quit IRC17:16
*** wavedrom has joined #yosys17:26
*** leviathanch has quit IRC17:54
*** emeb_mac has quit IRC18:23
*** X-Scale has quit IRC18:30
*** X-Scale has joined #yosys18:34
*** pie_ has quit IRC18:52
*** pie_ has joined #yosys18:52
*** cr1901_modern has quit IRC19:39
*** xerpi has joined #yosys19:50
*** lutsabound has quit IRC20:36
*** lutsabound has joined #yosys21:05
*** xerpi has quit IRC21:09
*** xerpi has joined #yosys21:16
*** xerpi has quit IRC21:40
*** xerpi has joined #yosys21:41
*** angelterrones has joined #yosys22:02
*** angelterrones has quit IRC22:08
*** angelterrones has joined #yosys22:09
*** vup has quit IRC22:50
*** cr1901_modern has joined #yosys22:54
*** vup2 has quit IRC23:06
*** vup2 has joined #yosys23:06
*** lutsabound has quit IRC23:16
*** angelterrones has quit IRC23:30
*** lutsabound has joined #yosys23:31
*** cmuellner has joined #yosys23:32
*** xerpi has quit IRC23:55

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