• 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 SKILL
  3. poCellNameMap not resolving cell name collisions

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13289
  • 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

poCellNameMap not resolving cell name collisions

JayR
JayR over 10 years ago

When I use Xstream to stream out, Xstream is adding a bunch of _cv1, _cv2, et. al. suffixes, even when the cell name collisions are not real.   In other words, the lib, cell, and view are all exactly identical, but XStream still treats these as collisions when in fact I only need one STRUCTURE streamed out in the first place.  After all, it's the exact same cell.

I tried to resolve this using poCellNameMap, and even then XStream still tacks on _cv1, _cv2, etc. even after poCellNameMap puts its own sauce on it.   For the life of me, I can't get rid of these stupid suffixes without postprocessing the GDS.   

Surely there is a much simpler solution to this?     Haven't others seen this problem before?

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Really? The only reason I can see that Xstream would do this is if the lib/cell/view in question is a PCell (a Parameterised Cell), because then it needs to write out a different structure (stream name for a "cell") for each variant (based on the parameters passed to the PCell), and so would need a unique name. If it's the same lib/cell/view referenced in multiple instantiations, then there would be no collision and no need to write it out more than once. I've never seen it doing that, and it would be a bug if that was happening - you should report this to customer support.

    Using poCellNameMap won't allow you merge different masters into one - if it thinks there's a good reason to write out multiple structures, it will continue to do so, and of course it needs to ensure they have unique names.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Really? The only reason I can see that Xstream would do this is if the lib/cell/view in question is a PCell (a Parameterised Cell), because then it needs to write out a different structure (stream name for a "cell") for each variant (based on the parameters passed to the PCell), and so would need a unique name. If it's the same lib/cell/view referenced in multiple instantiations, then there would be no collision and no need to write it out more than once. I've never seen it doing that, and it would be a bug if that was happening - you should report this to customer support.

    Using poCellNameMap won't allow you merge different masters into one - if it thinks there's a good reason to write out multiple structures, it will continue to do so, and of course it needs to ensure they have unique names.

    Regards,

    Andrew.

    • 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