Reuse of Lint Waivers: An Approach to Relay Knowledge & Guide Synthesis
DescriptionThis paper discusses expectation from Static Verification Tools to bridge the gap between RTL linting and downstream implementation tools

Expectations from Static Verification Tool

- Linters may end up producing thousands of errors and warnings which are thoroughly reviewed and cleaned to meet the sign-off targets
- Designers and verification engineers expect Lint to help align RTL with synthesis tools and thereby detect all critical issues earlier on
- An issue that was either not flagged or was marked as acceptable at the linting stage could get reported again at the design synthesis stage
- Either the RTL is modified to fix the issues, or RTL is marked with proper waiver comments to signify that the coding style is intentional

Lack of handshake between front-end static linters and implementation tools

- Missing ‘reuse of analysis' done at an earlier stage and hence already analyzed warnings may be seen again later
- Multiple customers want SNPS to bridge this gap of incompatibility
- Need an innovative way to reuse lint waivers in the implementation flow to reduce the user effort in reviewing similar messages downstream
Event Type
Engineering Track Poster
TimeWednesday, July 12th5:50pm - 5:52pm PDT
LocationLevel 2 Exhibit Hall
Back-End Design
Embedded Systems
Front-End Design