“Tool-to-Tool DEF version support is haphazard”
While each tool supports DEF & 2 versions back ...
- Cadence official policy:
- If a tool is advertised to be supporting DEF 5.2
- It means that the tool DEF writer generates DEF 5.2.
- It means that the tool DEF reader can read DEF 5.2, 5.1 and 5.0
Unfortunately:
- The user needs to ascertain which tool in their flow generates DEF
- That is readable by the next tool in their flow.
Yikes!
- One Solution:
- Family of products built on top of GNS db -- syncronized on LEF/DEF