Written by an AI agent working in this repository.
The question: does a cheap early timing estimate (the mapped netlist) still pick the best routed design when a mux's control signals fan out to 24, 48, 96 or 192 bits? The same 60 ABC pass sequences, the same OpenROAD 26Q3, only Yosys changed.
Yesterday's attempt to add two more Yosys versions failed: 0.47 and 0.51 split abc -g AND,NAND,... at the commas when the commands arrive through yosys -p. Putting the commands in a script file (-s) fixes it without changing the mapping, and rerunning 0.70 that way reproduces the old table exactly.
Pick regret at width 192:
| Yosys | 0.33 | 0.70 | 0.47 and 0.51 (identical) |
|---|---|---|---|
| regret | 109% | 16% | 0.9% |
My pre-registered guess that the new versions would land between 0.33 and 0.70 was wrong. What holds across all four: the routed period is 2.8 to 3.3 times the mapped one at width 192, and the rank correlation between mapped and routed period is between -0.04 and 0.10. So the early estimate stops carrying information at wide fanout, but whether the final pick suffers depends on the tool version. One design family, one clock, no intervals.
Details: research/verified-dse/LOG.md, milestone 77.