Merged
Conversation
This was
linked to
issues
Apr 2, 2022
… mapping file, nothing else
REGIONS in map files -> REGION REGION NONE for map files (maps REGIONs which are neither GUIDE or FENCE) Bugfix: VIA with ORIGIN No via cell name prefix by default for buddy tools
Dropped --lefdef-dont-produce-instance-names, --lefdef-dont-produce-pin-names and --lefdef-dont-produce-net-names options. Instead, these options have to be enabled by giving the respective property names. Writing the property names takes some space and these options are simply confusing and redundant.
…NAME (which is ignored)
klayoutmatthias
added a commit
that referenced
this pull request
Apr 23, 2022
* Implementated patch as suggested by issue-1047 * Implementing blend-mode for LEF/DEF for a first solution for issue-1048 * Added testcase, fixed other tests * Issue-1050 fixed - now REGION, BLOCKAGE and DIEAREA are relevant from mapping file, nothing else * Bug fixes * Experimental: DEF multipart paths * Experimental: ignore LEF wire extension, ignore PATTERNNAME * Implemented PATTERNNAME in DEF instead of LEF .. * Implemented nondefaultrule vias * LEF/DEF: non-defaultrule vias need a name suffix. * Refined solution for NDR via names, updated test data * Updated test data * Multiple map files and 'REGIONS FENCE' + 'REGIONS GUIDE' layer mapping entries. * Added test data, updated doc. * Some enhancements and feedback REGIONS in map files -> REGION REGION NONE for map files (maps REGIONs which are neither GUIDE or FENCE) Bugfix: VIA with ORIGIN No via cell name prefix by default for buddy tools * Simplified buddy tool options for LEF/DEF property names Dropped --lefdef-dont-produce-instance-names, --lefdef-dont-produce-pin-names and --lefdef-dont-produce-net-names options. Instead, these options have to be enabled by giving the respective property names. Writing the property names takes some space and these options are simply confusing and redundant. * Issue a warning about missing cut geometry for a DEF via with PATTERNNAME (which is ignored) * Fixed issue-1065
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.