feat!: make substitutions more predictable, strictly class-level

[donn]

Misc. Enhancements/Bugfixes

• openlane.flows

  • SequentialFlow
    • Substitutions are now to be strictly consumed by the subclass initializer,
      i.e., it can no longer be done on the object-level and only on the class
      level. Additionally, it can provided as a list of tuples instead of a
      dictionary so the same key may be reused multiple times.
    • Step IDs are re-normalized after every substitution, so a substitution for
      OpenROAD.DetailedPlacement-1 for example would always refer to the
      second OpenROAD.DetailedPlacement AFTER applying all previous
      substitutions, instead of the second "original"
      OpenROAD.DetailedPlacement in the flow.

• openlane.config

  • meta.substituting_steps now only apply to the sequential flow declared in
    meta.flow and not all flows.

---

Resolves #646

[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-remote current --branch dev --table-verbosity ALL --table-out ./tables_all.md.

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

Full tables ► https://gist.github.com/openlane-bot/64d795876674042cab631d968a702b3a