Multi-corner STA Pre-PnR

[donn]

• OpenROAD.STAPrePnR
  • Now performs multicorner STA pre-PnR according to STA_CORNERS; although if two corners have identical file lists the latter corner is skipped
  • Internally rearranged class structure so STA pre and post PnR share as much code as possible

Misc

• openlane.steps
  • Step
  • .start() no longer prints logs at the beginning as it may not necessarily exist

---

Resolves #447

[openlane-bot]

Metric comparisons are in beta. Please report bugs under the issues tab.

To create this report yourself, grab the metrics artifact from the CI run, extract them, and invoke python3 -m openlane.common.metrics compare-main <path to directory>.

• No changes to critical metrics were detected in analyzed designs.

Full tables ► https://gist.github.com/openlane-bot/3c7b4e5cab6d45b9e5746c4c777426de

[kareefardi]

• OpenROAD.STAPrePnR

  • Now performs multicorner STA pre-PnR according to STA_CORNERS; although if two corners have identical file lists the latter corner is skipped
  • Internally rearranged class structure so STA pre and post PnR share as much code as possible

Misc

* `openlane.steps`

  * `Step`

    * `.start()` no longer prints logs at the beginning as it may not necessarily exist
    * `.run_subprocess()` now prints the log path at log level `DEBUG`

Resolves #447

• How does this lead to changes in critical metrics?
• Why the change from verbose to debug in the log path print?

[donn]

Why the change from verbose to debug in the log path print?

Bit of a tendency to clog up the terminal, especially for steps and flows that use multithreading

[kareefardi]

Why the change from verbose to debug in the log path print?

Bit of a tendency to clog up the terminal, especially for steps and flows that use multithreading

Debug clogs up the terminal even more and having the clickables of the log files is more useful than running with log level debug