• 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. Custom IC Design
  3. skip=cut inst=[...] statements being ignored

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 1678
  • 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

skip=cut inst=[...] statements being ignored

wignesb
wignesb over 3 years ago

The following skip statement (included via "definitions file") works fine :-

       myScopedOpts options skip=cut inst=[i10.i0*] 

But it does not work when I try to use this:-

     myScopedOpts options skip=cut inst=[i10.i0\<3\> i10.i0\<2\>]         

I get the following warning message in the spectre.out file:-

Warning from spectre during hierarchy flattening.
WARNING (SFE-465): Can not find local option scope `i10.i0<2>' of options statement(options ignored).
WARNING (SFE-465): Can not find local option scope `i10.i0<3>' of options statement(options ignored).

I've also tried cutting all of them and then use skip=none for those I want included (same problem).

Any idea where I'm going wrong. 

Thank you.                                                                                                                

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    I just tried this with SPECTRE20.1 ISR11, and it works fine. I did initially get the warning you did, but that was because my instances were called I10 not i10 - the statements are case-sensitive. So check that you've actually got the case of the instance names correct (given that the default is normally for them to begin with uppercase "I" I would expect that I10.I0\<3\> would be more likely).

    If that doesn't work (given that the first approach did work, maybe your instance names really are in lowercase), please let me know which spectre sub-version you're using (it's shown at the top of the spectre log file)

    Thanks,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wignesb
    wignesb over 3 years ago in reply to Andrew Beckett

    Andrew,

    i am using Version 19.1.0.641.spe.isr18. My case usage is correct. 

    I tried Version 21.1.0.156  and it works there.

    Thank you 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to wignesb

    Ah yes, I see that too with that version. That's why it's always useful to follow the forum guidelines and mention which software versions you're using!

    Anyway, glad you're able to run using a later version.

    Regards,

    Andrew

    • 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