Howdy everyone! I’ve been working on hardening a sky130 design that has some long chains of (only) unclocked combo logic and I’ve noticed with OpenLane that if I specify a CLOCK_PERIOD of 20ns, it fails with setup violations, and comes back to report a “suggested_clock_period” on the order of 28ns. Ok, I’m not surprised. However, if I set CLOCK_PERIOD to something ridiculous like 0.05ns, it does change the layout and reports a “suggested_clock_period” of just under 20ns… as though specifying an impossibly fast timing requirement made it try much harder and came up with a layout that was in fact ~30% faster. But… is this likely to be bogus?