• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. LEC - confusion with rtl vs netlist

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 2870
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LEC - confusion with rtl vs netlist

bharat1001
bharat1001 over 13 years ago
Hi, I have a golden RTL. I synthesize this RTL using Synplify and get a netlist, A. Using the VIF flow, I run LEC and find that netlist A and the RTL are equivalent. I then synthesize the same golden RTL using different synthesis options and the same synthesizer and get a netlist, B. LEC shows that netlist B and the golden are not equivalent. I then attempt to LEC netlist A and netlist B expecting mismatches, however LEC says they are equivalent! With respect to unmapped key points, I do have them, but in the golden RTL and both netlists, they are all unreachable. What can cause netlist A and B to be equivalent? Thanks
  • Cancel
  • croy
    croy over 13 years ago
    Hi Bharat It's quite common to have rtl-synth1 and rtl-synth2 pass while synth1-synth2 fails (dont-care optimized differently) or aborts (datapath optimized differently). Both netlists are fine, just implemented a little different. I'm scratching my head as to your description of rtl-synth1 and synth1-synth2 passing and rtl-synth2 failing. That's a new one. Can you create a Service Request please so someone looks at the logs? Thanks, Chrystian
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information