Skip to content

synth: more consistent naming#3295

Closed
oharboe wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
Pinata-Consulting:logs-naming
Closed

synth: more consistent naming#3295
oharboe wants to merge 1 commit into
The-OpenROAD-Project:masterfrom
Pinata-Consulting:logs-naming

Conversation

@oharboe
Copy link
Copy Markdown
Collaborator

@oharboe oharboe commented Jul 7, 2025

I'm not keen on changing 1_1_yosys stem as I don't know what tools that rely on that name, like metrics, but canonicalization happens before 1_1_yosys, so the compromise is to create 1_0_yosys_canonicalize stem.

I'm not keen on changing 1_1_yosys stem as I don't know what tools
that rely on that name, like metrics, but canonicalization
happens before 1_1_yosys, so the compromise is to create
1_0_yosys_canonicalize stem.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
@oharboe oharboe requested a review from maliberty July 7, 2025 15:25
@maliberty
Copy link
Copy Markdown
Member

1_0 is inconsistent with how we name substeps in all other steps in the flow. I find that more objectionable than have 1_1 become 1_2. We have added/removed steps in the flow before so its possible.

@oharboe oharboe closed this Jul 7, 2025
@oharboe
Copy link
Copy Markdown
Collaborator Author

oharboe commented Jul 7, 2025

1_0 is inconsistent with how we name substeps in all other steps in the flow. I find that more objectionable than have 1_1 become 1_2. We have added/removed steps in the flow before so its possible.

I'll look at that tomorrow. I want to have this in the can before I create a followup to #3294 to do hashes for synthesis

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.

2 participants