• 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. Incomprehensible warning when running "write hier_compare...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 61
  • Views 7569
  • 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

Incomprehensible warning when running "write hier_compare dofile"

archive
archive over 18 years ago

Hi

When I ran write hier_compare command, I found the tool firing the following warning. May I know the reason for such a behavior. 

Warning: Golden or Revised have modules with number of instances less than 50. Skip it for hierarchical comparison

Thanks
Prasad.


Originally posted in cdnusers.org by anssprasad
  • Cancel
  • archive
    archive over 18 years ago

    In order to decrease the number of sub-blocks to comapre Conformal has a threshold.
    All module with number of primitives less than the treshold are flattened and the "father" module is compared. This is bad syntax of the message, actualy nothing is skipped, don't worry :)


    Originally posted in cdnusers.org by Stalker
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Maxim,

    According what I see in the dofile generated by the tool as a result of the command I used: -

    write hier_compare dofile abrisccore3.one -module abrisccore3 abrisccore3 -hier -noexact_pin_match

    I don't find the modules it listed in the transcript following this warning. I am afraid they are really being skipped from comparison.

    Thanks
    Prasad.


    Originally posted in cdnusers.org by anssprasad
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Prasad,
    These modules are not written into dofile, but the mapped points of these modules are compared together with the mapped points of the "parent" module - the one which instantiate the "skipped" module.
    Again, no key point is skipped from comparrison.
    You can send this warning to Cadence support and ask them.

    Regards,


    Originally posted in cdnusers.org by Stalker
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Prasad

    Maxim is correct: the module simply gets compared as part of its parent. Saying 'skipped' is bad syntax and there's been internal discussions about changing that.

    The default threshold is 50 but that can be changed using the -threshold switch. There's usually no reason to do that except for library qualification, where you do want verification to be run, separately, on every single cell.

    Chrystian


    Originally posted in cdnusers.org by croy
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Thanks Maxim,

    I got you. But, is there any way to tell the tool not to bother itself about simplifying my work!!

    Prasad.


    Originally posted in cdnusers.org by anssprasad
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Thanks Chrystian, I think that dispels all my doubts.


    Originally posted in cdnusers.org by anssprasad
    • 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