48abe30ea4
"bloat-all" which is "bloat-all types1 types2 distance" where the "distance" value is a maximum amount to grow. It is not (that I know of) particularly useful for generating output GDS, but it is very useful for generating temporary layers for DRC checks, especially things like determining tap distance for latch-up rules. The alternative (used in the sky130 tech file) is a tedious step-by-step "grow" followed by "and-not". This rule option is much cleaner to implement and computes faster (although it is still a boolean operator and is much slower than an edge rule). |
||
|---|---|---|
| .. | ||
| CIFgen.c | ||
| CIFhier.c | ||
| CIFint.h | ||
| CIFmain.c | ||
| CIFrdcl.c | ||
| CIFrdpoly.c | ||
| CIFrdpt.c | ||
| CIFrdtech.c | ||
| CIFrdutils.c | ||
| CIFread.h | ||
| CIFsee.c | ||
| CIFtech.c | ||
| CIFwrite.c | ||
| Makefile | ||
| cif.h | ||