Adjust interpretation of SYNTH_KEEP_MODULES#3384
Conversation
Only apply `SYNTH_KEEP_MODULES` when `SYNTH_HIERARCHICAL=1`. Also make this variable override the list of kept modules selected by the `SYNTH_MINIMUM_KEEP_SIZE` threshold. This is done to reduce user confusion. Signed-off-by: Martin Povišer <povik@cutebit.org>
Signed-off-by: Martin Povišer <povik@cutebit.org>
|
FYI @oharboe @jeffng-or |
|
We could go further and make setting |
I use SYNTH_KEEP_MODULES to ensure they are not flattened together or without SYNTH_HIERACHICAL to automatically flatten small modules Also, I do parallel abc builds in bazel where I use SYNTH_KEEP_MODULES as part of the mechanics. Parallel abc is MUCH faster on my design. |
oharboe
left a comment
There was a problem hiding this comment.
So I may need infinite minimum keep size if I want to manually list keep modules?
Confusing.
Maybe SYNTH_HIERARCHICAL should be removed?
We either keep modules or not based on automatic and/or manual criteria?
The state after this change would be: Let me know if this sounds good. This is in response to a seasoned user of ORFS being confused by how the options currently work (if you want manual selection, you need to define KEEP_MODULES and disable SYNTH_HIERARCHICAL) |
@oharboe I see so with this change we won't be able to support your "together" use case. |
Yes. We either keep modules or not and we have manual and/or automatic criteria. The default minimum automatic keep size is a PDK specific default. |
|
We need a different change then. |
Only apply
SYNTH_KEEP_MODULESwhenSYNTH_HIERARCHICAL=1. Also make this variable override the list of kept modules selected by theSYNTH_MINIMUM_KEEP_SIZEthreshold. This is done to reduce user confusion.