• 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. PVS LVS Deck behaviour

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14408
  • 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

PVS LVS Deck behaviour

Suryansh Singh
Suryansh Singh over 5 years ago

Hi ,

I had a question regarding PVS LVS rules writing behavior. I have a deck from foundry which has some code in the following manner :

not A B -output A1

not A B -output A2 

not A B -output A3 

i.e. same layers with same operation resulting in three different output layers. I ran LVS with Layer viewer and I can see only the A1 layer in the layer viewer. 

Now my question is why I do not see A2 and A3? Could it somehow be dependent on operations that happen next  on A1,A2 and A3? Would this also happen if the operation was something else (like AND)? 

Regards

Suryansh Singh

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Suryansh,

    I've not done detailed checking on what happens with PVS rule optimisation, but it wouldn't surprise me if it optimised away the operations if the results are not used. Did you check to see if A2 and A3 are used? This may be best followed up with customer support so that we can see your actual rules in operation. I don't think it's anything to do with the operation used (i.e. AND rather than NOT).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Suryansh Singh
    Suryansh Singh over 5 years ago in reply to Andrew Beckett

    Thanks Andrew

    I will explore a bit about PVS rule optimization and see if that answers my questions completely.

    Regards

    Suryansh Singh

    • 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