Skip to content

Fix uW, ca53, bp_single and bp_dual metric failures #4357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
arthurjolo wants to merge 5 commits into from
Closed

Fix uW, ca53, bp_single and bp_dual metric failures #4357

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
779a4a8
bump OR version
arthurjolo Jul 14, 2026
e0e2777
designs/gf12/bp_single/rules-base.json updates:
arthurjolo Jul 14, 2026
9380a10
designs/gf12/ca53/rules-base.json updates:
arthurjolo Jul 14, 2026
b827522
designs/gf12/bp_dual/rules-base.json updates:
arthurjolo Jul 14, 2026
c4edb2d
Merge branch 'master' into fix_ci_failures
maliberty Jul 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions flow/designs/gf12/bp_dual/rules-base.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,11 @@
"compare": "<="
},
"cts__timing__setup__ws": {
"value": -614.0,
"value": -750.0,

@gemini-code-assist gemini-code-assist Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This timing baseline shows a significant degradation from -614.0 to -750.0 (~22.1%). Per the general rules, merging updates to regression baselines with significant degradation requires an explicit agreement or tracking issue to address the underlying issue later. A tracking issue or explicit agreement needs to be established and referenced before merging.

References
  1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

"compare": ">="
},
"cts__timing__setup__tns": {
"value": -1500000.0,
"value": -1670000.0,

@gemini-code-assist gemini-code-assist Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This timing baseline shows a significant degradation from -1500000.0 to -1670000.0 (~11.3%). Per the general rules, merging updates to regression baselines with significant degradation requires an explicit agreement or tracking issue to address the underlying issue later. A tracking issue or explicit agreement needs to be established and referenced before merging.

References
  1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

"compare": ">="
},
"cts__timing__hold__ws": {
Expand All @@ -58,11 +58,11 @@
"compare": "<="
},
"globalroute__timing__setup__ws": {
"value": -201.0,
"value": -117.0,
"compare": ">="
},
"globalroute__timing__setup__tns": {
"value": -6470.0,
"value": -541.0,
"compare": ">="
},
"globalroute__timing__hold__ws": {
Expand Down Expand Up @@ -94,7 +94,7 @@
"compare": ">="
},
"finish__timing__setup__tns": {
"value": -1160.0,
"value": -989.0,
"compare": ">="
},
"finish__timing__hold__ws": {
Expand Down
10 changes: 5 additions & 5 deletions flow/designs/gf12/bp_single/rules-base.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,15 +42,15 @@
"compare": ">="
},
"cts__timing__setup__tns": {
"value": -474000.0,
"value": -389000.0,
"compare": ">="
},
"cts__timing__hold__ws": {
"value": -299.0,
"compare": ">="
},
"cts__timing__hold__tns": {
"value": -4700.0,
"value": -763.0,
"compare": ">="
},
"globalroute__antenna_diodes_count": {
Expand All @@ -62,11 +62,11 @@
"compare": ">="
},
"globalroute__timing__setup__tns": {
"value": -79400.0,
"value": -48500.0,
"compare": ">="
},
"globalroute__timing__hold__ws": {
"value": -275.0,
"value": -375.0,

@gemini-code-assist gemini-code-assist Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This timing baseline shows a significant degradation from -275.0 to -375.0 (~36.4%). Per the general rules, merging updates to regression baselines with significant degradation requires an explicit agreement or tracking issue to address the underlying issue later. A tracking issue or explicit agreement needs to be established and referenced before merging.

References
  1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

"compare": ">="
},
"globalroute__timing__hold__tns": {
Expand Down Expand Up @@ -94,7 +94,7 @@
"compare": ">="
},
"finish__timing__setup__tns": {
"value": -1430.0,
"value": -1850.0,

@gemini-code-assist gemini-code-assist Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This timing baseline shows a significant degradation from -1430.0 to -1850.0 (~29.3%). Per the general rules, merging updates to regression baselines with significant degradation requires an explicit agreement or tracking issue to address the underlying issue later. A tracking issue or explicit agreement needs to be established and referenced before merging.

References
  1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

"compare": ">="
},
"finish__timing__hold__ws": {
Expand Down
6 changes: 5 additions & 1 deletion flow/designs/gf12/ca53/rules-base.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@
"compare": "==",
"level": "warning"
},
"synth__design__instance__area__stdcell": {
"value": 174000.0,
"compare": "<="
},
"constraints__clocks__count": {
"value": 1,
"compare": "=="
Expand Down Expand Up @@ -98,7 +102,7 @@
"compare": ">="
},
"finish__timing__hold__tns": {
"value": -4350.0,
"value": -5290.0,

@gemini-code-assist gemini-code-assist Bot Jul 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This timing baseline shows a significant degradation from -4350.0 to -5290.0 (~21.6%). Per the general rules, merging updates to regression baselines with significant degradation requires an explicit agreement or tracking issue to address the underlying issue later. A tracking issue or explicit agreement needs to be established and referenced before merging.

References
  1. It is acceptable to merge updates to regression baselines that show significant degradation, provided there is an explicit agreement to address the underlying issue later.

"compare": ">="
},
"finish__design__instance__area": {
Expand Down
2 changes: 1 addition & 1 deletion tools/OpenROAD
Open in desktop
Submodule OpenROAD updated 170 files