Skip to content

Conversation

@oharboe
Copy link
Collaborator

@oharboe oharboe commented Dec 30, 2025

no longer save out all .odb/.sdc files automatically, the user can save out as many or as few as they need.

@oharboe oharboe requested a review from maliberty December 30, 2025 11:21
@oharboe oharboe force-pushed the single-openroad-invocation-flows branch from 2f656fd to 08f742e Compare December 30, 2025 11:46
This commit is only to simplify the review.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
no longer save out all .odb/.sdc files automatically,
the user can save out as many or as few as they need.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
@oharboe oharboe force-pushed the single-openroad-invocation-flows branch from 08f742e to b7a8ba7 Compare December 30, 2025 11:54
@maliberty
Copy link
Member

no longer save out all .odb/.sdc files automatically

I don't see a change in the default flow. I suppose you mean it in the context of the SINGLE_OPENROAD_INVOCATION_FLOW.

SINGLE_OPENROAD_INVOCATION_FLOW doesn't actually control the invocation of OR so it feels odd. Further you might want a single invocation flow to write out an .odb at each step even if it doesn't exit, so this feels orthogonal.

erasing variables or not and saving sdc/odb after each stage are now different
variables

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
@oharboe
Copy link
Collaborator Author

oharboe commented Dec 30, 2025

no longer save out all .odb/.sdc files automatically

I don't see a change in the default flow. I suppose you mean it in the context of the SINGLE_OPENROAD_INVOCATION_FLOW.

SINGLE_OPENROAD_INVOCATION_FLOW doesn't actually control the invocation of OR so it feels odd. Further you might want a single invocation flow to write out an .odb at each step even if it doesn't exit, so this feels orthogonal.

Fixed.

@@ -1,5 +1,6 @@
# Enable keeping variables between stages
set ::env(KEEP_VARS) 1
set ::env(WRITE_ODB_AND_SDC_EACH_STAGE) 0
Copy link
Member

Choose a reason for hiding this comment

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

This will prevent the user from overriding it. I think this should only be set if currently unset.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Consistent with other variables, I have added default values in variables.yaml as a perference, so if I check if these values are set, they always are. Hence, I set them to explicitly here, which I think is the intent of the script.

Do you have any more information about the use-case of this script, I'm guessing here.

Copy link
Member

Choose a reason for hiding this comment

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

The intent of the script is to perform all operations in a single invocation. Whether to write odb at each stage or not is a separate decision. @eder-matheus does this matter for you?

Copy link
Member

Choose a reason for hiding this comment

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

In the scenario I'm using it, I'm interested on the ODB files of each stage. However, I'm not against having it as an option, and the default behavior would be not writing the ODBs of each stage.

This PR now adds the option of skipping saving of
.odb/.sdc files only

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
@oharboe
Copy link
Collaborator Author

oharboe commented Dec 31, 2025

@eder-matheus @maliberty Should be all good now. Anything else?

@maliberty maliberty merged commit 8d5b198 into The-OpenROAD-Project:master Dec 31, 2025
8 checks passed
@oharboe oharboe deleted the single-openroad-invocation-flows branch January 1, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants