• 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. List forming was changed in IC 6.1.5.65?

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 13915
  • 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

List forming was changed in IC 6.1.5.65?

Slayer
Slayer over 14 years ago

 Hi all!

Could u pls. help me with  one issue. The questionis, that succession of shapes in list is change in IC6.1.5.65. I try to clarify this moment.

In pcell I use some subCells, after that pull up need shepes and forming list formshapes

example:

[CODE]

        shapesToCopy = setof(i car(instances)->master->shapes i->up||i->conn);
        foreach(i if(oddp(ng) cdr(reverse(instances)) instances)
            foreach(s shapesToCopy
                dbCopyFig(s pcCV list(i->xy "R0"));
            );
        );

[/CODE]

after that according to property on shapes I sort it in lists

[CODE] 

         foreach(s setof(i pcCV->shapes i->conn)
            case(s->conn
                ("gTop"
                    gatesTop = cons(s gatesTop);
                )
                ("gBot"
                    gatesBot = cons(s gatesBot);
                )
                ("sub"
                    substrates = cons(s substrates);
                )
            );end case
        );end foreach

[/CODE]

And In cdb version (on this version all works fine)  I have succession of shapes which were builded from left to right, but in IC6.1.5.65 shape which was on first position now on second, wich was on 4 position now on 3 and etc.

What's wrong? What were changed, and how to use pcells which were created under cdb version?

  • Cancel
Parents
  • Slayer
    Slayer over 14 years ago

     Yes, function sort() is work around for this case, but I have a lot of devices in library, and now I must change a lot of pcell code and make db compare of layout to be insured that will no impacts for designers.

    Simple when we create shapes they have id number which increased step to step and when we takes shapes for process, for example: ccv()->shapes, I think this list should have shapes already sorted by id number isn't it? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Slayer
    Slayer over 14 years ago

     Yes, function sort() is work around for this case, but I have a lot of devices in library, and now I must change a lot of pcell code and make db compare of layout to be insured that will no impacts for designers.

    Simple when we create shapes they have id number which increased step to step and when we takes shapes for process, for example: ccv()->shapes, I think this list should have shapes already sorted by id number isn't it? 

    • 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