• 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. TIP OF THE MONTH : Reporting similarity between two designs...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 13045
  • 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

TIP OF THE MONTH : Reporting similarity between two designs (new for v7.1!)

archive
archive over 18 years ago

BONUS TIP : Type "help whatsnew" in Conformal LEC version 7.1 and onwards to get all the new commands! - - - TIP OF THE MONTH : Reporting similarity between two designs Situation: You may have two gate-level netlists that are from different stages of the design flow (for example: post-synthesis netlist and post-layout netlist). Or you may have two netlists from different synthesis runs that are using different optimization techniques. Or you may receive two netlist that you have no information about (such as two netlist, on that has been ECO'd). Perhaps you have non-equivalents, or are experiencing long compare run times, maybe due to complex datapaths. For whatever reason, your goal is to "measure" the similarity between two designs. A method is to use Conformal LEC's new command: "report design similarity" The measurement results are expressed as a % value between 0 and 100. Design similarity is quantified by comparing the corresponding points between the two designs. The two designs do not need to be equivalent in order to execute this command. LEC Command: > REPORT DESIGN SIMILARITY (new command for LEC 7.1) Switches: "-Golden" -means Revised design (design on right side) is used as reference. -default is the above "-INStance " -if you wish to target an instance -default is the entire design Usage: -execute command after switching to LEC mode. -can be useful for debugging and profiling. Example: report design similarity -Golden -Instance mult* -this displays all the similarities between instances with this name. -this is useful if you have components such as multipliers which you want to profile. For even more detailed information, in LEC type: > HELP DESIGN SIMILARITY FEEDBACK from the Readers: This is a new command which we think users will find creative uses for... If so, please post your feedback to this thread. Thanks!


Originally posted in cdnusers.org by kchang
  • Cancel
Parents
  • MaheshSiddappa
    MaheshSiddappa over 13 years ago

    Some additional features for two equivalent netlists would be useful

    1. DFF Counts, and the list of constant flops, merged flops to account for the difference in flop counts.

    2. Instances per each module in the two verilog netlists

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • MaheshSiddappa
    MaheshSiddappa over 13 years ago

    Some additional features for two equivalent netlists would be useful

    1. DFF Counts, and the list of constant flops, merged flops to account for the difference in flop counts.

    2. Instances per each module in the two verilog netlists

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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