#68 yosys_rewrite_verilog.tcl step seems to get st...
# openlane
g
#68 yosys_rewrite_verilog.tcl step seems to get stuck Issue opened by growly I'm on rc3 - The
yosys_rewrite_verilog.tcl
step of this flow is taking a strangely long time. yosys is consuming ~92 GB of RAM and has been spinning a core at ~100% for 16.5 hours. The command is
yosys -c /openLANE_flow/scripts/yosys_rewrite_verilog.tcl -l /openLANE_flow/designs/151/runs/06-10_16-40/logs/synthesis/yosys_rewrite_verilog.log
, but the log file is empty. I believe it's still in the
read_verilog
step of the script but I can't really be sure. The design is the same as in #39. I had a stab at debugging yosys; it gets stuck in a recursive call and I couldn't observe progress over a few hours. It might just be really slow. I built Yosys at HEAD instead and this problem seems to have gone away, with the rewrite step now completing in ~7 hours. Has anyone else run into this problem with the yosys commit in rc3? (347dd01c2f7dff6e8222c5f9d360f84a17c937b5) efabless/openlane