IC Compiler™ II

Library Preparation
User Guide
Version M-2016.12-SP4, June 2017
Copyright Notice and Proprietary Information
©2017 Synopsys, Inc. All rights reserved. This Synopsys software and all associated documentation are proprietary to
Synopsys, Inc. and may only be used pursuant to the terms and conditions of a written license agreement with
Synopsys, Inc. All other use, reproduction, modification, or distribution of the Synopsys software or the associated
documentation is strictly prohibited.
Destination Control Statement
All technical data contained in this publication is subject to the export control laws of the United States of America.
Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader's responsibility to
determine the applicable regulations and to comply with them.
Disclaimer
SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH
REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Trademarks
Synopsys and certain Synopsys product names are trademarks of Synopsys, as set forth at
http://www.synopsys.com/Company/Pages/Trademarks.aspx.
All other product or company names may be trademarks of their respective owners.
Third-Party Links
Any links to third-party websites included in this document are for your convenience only. Synopsys does not endorse
and is not responsible for such websites and their practices, including privacy practices, availability, and content.

Synopsys, Inc.
690 E. Middlefield Road
Mountain View, CA 94043
www.synopsys.com

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 ii

Synopsys® Free and Open-Source Licensing Notices for IC Compiler™ II Products
Contents
Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
FOSS Package Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
GNU Bison 3.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Flex 2.5.37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
LEF/DEF Reader 5.8-p008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
mcpp 2.7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Oasis Wrapper 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Threading Building Blocks 4.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
TCL/TK 8.5.12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
zlib 12.5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
libedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Document Overview
This document includes licensing information relating to free and open-source software (“FOSS”) included with
Synopsys’s® IC Compiler II™ products (the “SOFTWARE”). The terms of the applicable FOSS license(s) govern
Synopsys’s® distribution and your use of the SOFTWARE. Synopsys® and the third-party authors, licensors, and
distributors of the SOFTWARE disclaim all warranties and all liability arising from any and all use and distribution of the
SOFTWARE. To the extent the FOSS is provided under an agreement with Synopsys® that differs from the applicable
FOSS license(s), those terms are offered by Synopsys® alone.

Synopsys® has reproduced below copyright and other licensing notices appearing within the FOSS packages. While
Synopsys® seeks to provide complete and accurate copyright and licensing information for each FOSS package,
Synopsys® does not represent or warrant that the following information is complete, correct, or error-free.
SOFTWARE recipients are encouraged to (a) investigate the identified FOSS packages to confirm the accuracy of the
licensing information provided herein and (b) notify Synopsys® of any inaccuracies or errors found in this document so
that Synopsys® may update this document accordingly.

Certain FOSS licenses (such as the GNU General Public License, GNU Lesser General Public License, and Eclipse
Public License) require that Synopsys® make the source code corresponding to the distributed FOSS binaries
available under the terms of the same FOSS license. Recipients who would like to receive a copy of such
corresponding source code should submit a request to Synopsys® by post at:

Synopsys
Attn: Open Source Requests
690 East Middlefield Road
Mountain View, CA 94043

Please provide the following information in all submitted FOSS requests:

• the FOSS packages for which you are requesting source code;
• the Synopsys® product (and any available version information) with which the requested FOSS packages are
distributed;
• an email address at which Synopsys® may contact you regarding the request (if available); and
• the postal address for delivery of the requested source code.

FOSS Package Notices

GNU Bison 3.0.4
Project homepage: https://www.gnu.org/software/bison/
Project license:

Copyright © 1998-2013 Free Software Foundation, Inc. This file is part of Bison, the GNU Compiler Compiler.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later
version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 iii

You should have received a copy of the GNU General Public License along with this program. If not, see <http://
www.gnu.org/licenses/>.

GNU GENERAL PUBLIC LICENSE

Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change
the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change
all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation,
use the GNU General Public License for most of our software; it applies also to any other work released this way by its
authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to
make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you
receive source code or can get it if you want it, that you can change the software or use pieces of it in new free
programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights.
Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to
respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients
the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you
must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps:(1) assert copyright on the software, and (2) offer
you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software.
For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their
problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them,
although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to
change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which
is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice
for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to
those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict
development and use of software on general-purpose computers, but in those that do, we wish to avoid the special
danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures
that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

0. Definitions.
"This License" refers to version 3 of the GNU General Public License.

"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you".
"Licensees" and "recipients" may be individuals or organizations.

To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission,
other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work
"based on" the earlier work.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 iv

A "covered work" means either the unmodified Program or a work based on the Program.

To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily
liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.
Propagation includes copying, distribution (with or without modification), making available to the public, and in some
countries other activities as well.

To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere
interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and
prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no
warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under
this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such
as a menu, a prominent item in the list meets this criterion.

1. Source Code.
The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means
any non-source form of a work.

A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body,
or, in the case of interfaces specified for a particular programming language, one that is widely used among developers
working in that language.

The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in
the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only
to enable use of the work with that Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A "Major Component", in this context, means a major
essential component (kernel, window system, and so on) of the specific operating system (if any) on which the
executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and
(for an executable work) run the object code and to modify the work, including scripts to control those activities.
However, it does not include the work's System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but which are not part of the work. For example,
Corresponding Source includes interface definition files associated with source files for the work, and the source code
for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by
intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the
Corresponding Source. The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided
the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program.
The output from running a covered work is covered by this License only if the output, given its content, constitutes a
covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license
otherwise remains in force. You may convey covered works to others for the sole purpose of having them make
modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do not control copyright. Those thus making or running
the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that
prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not
allowed; section 10 makes it unnecessary.

3. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling
obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
restricting circumvention of such measures.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 v

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the
extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you
disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users,
your or third parties' legal rights to forbid circumvention of technological measures.

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating
that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices
of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection
for a fee.

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of
source code under the terms of section 4, provided that you also meet all of these conditions:
a)The work must carry prominent notices stating that you modified it, and giving a relevant date.
b)The work must carry prominent notices stating that it is released under this License and any conditions added under
section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
c)You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.
This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and
all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other
way, but it does not invalidate such permission if you have separately received it.
d)If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has
interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions
of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a
storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to
limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a
covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also
convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a)Convey the object code in, or embodied in, a physical product (including a physical distribution medium),
accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software
interchange.
b)Convey the object code in, or embodied in, a physical product (including a physical distribution medium),
accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer
support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding
Source for all the software in the product that is covered by this License, on a durable physical medium customarily
used for software interchange, for a price no more than your reasonable cost of physically performing this conveying
of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c)Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an
offer, in accord with subsection 6b.
d)Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent
access to the Corresponding Source in the same way through the same place at no further charge. You need not
require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code
is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that
supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to
find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to
ensure that it is available for as long as needed to satisfy these requirements.
e)Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and
Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System
Library, need not be included in conveying the object code work.

A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally
used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In
determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 vi

particular product received by a particular user, "normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the way in which the particular user actually uses, or
expects or is expected to use, the product. A product is a consumer product regardless of whether the product has
substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use
of the product.

"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information
required to install and execute modified versions of a covered work in that User Product from a modified version of its
Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the
conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to
the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding
Source conveyed under this section must be accompanied by the Installation Information. But this requirement does
not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for
example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support
service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in
which it has been modified or installed. Access to a network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and protocols for communication across the
network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format
that is publicly documented (and with an implementation available to the public in source code form), and must require
no special password or key for unpacking, reading or copying.

7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more
of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were
included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to
part of the Program, that part may be used separately under those permissions, but the entire Program remains
governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy,
or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you
modify the work.) You may place additional permissions on material, added by you to a covered work, for which you
have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by
the copyright holders of that material) supplement the terms of this License with terms:
a)Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b)Requiring preservation of specified reasonable legal notices or author attributions in that material or in the
Appropriate Legal Notices displayed by works containing it; or
c)Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be
marked in reasonable ways as different from the original version; or
d)Limiting the use for publicity purposes of names of licensors or authors of the material; or
e)Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified
versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual
assumptions directly impose on those licensors and authors.

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the
Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a
term that is a further restriction, you may remove that term. If a license document contains a further restriction but
permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of
that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement
of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as
exceptions; the above requirements apply either way.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 vii

8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt
otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including
any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if
the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you
of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for
any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or
rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not
qualify to receive new licenses for the same material under section 10.

9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a
covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does
not require acceptance. However, nothing other than this License grants you permission to propagate or modify any
covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or
propagating a covered work, you indicate your acceptance of this License to do so.

10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run,
modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third
parties with this License.

An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or
subdividing an organization, or merging organizations. If propagation of a covered work results from an entity
transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work
the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with
reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For
example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License,
and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is
infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents.
A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the
Program is based. The work thus licensed is called the contributor's "contributor version".

A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already
acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or
selling its contributor version, but do not include claims that would be infringed only as a consequence of further
modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent
sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential
patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its
contributor version.

In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated,
not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent
infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to
enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not
available for anyone to copy, free of charge and under the terms of this License, through a publicly available network
server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available,

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 viii

or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly
relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a
country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring
conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work
authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you
grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may
not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing
software, under which you make payment to the third party based on the extent of your activity of conveying the work,
and under which the third party grants, to any of the parties who would receive the covered work from you, a
discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from
those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered
work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement
that may otherwise be available to you under applicable patent law.

12. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this
License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to
satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence
you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further
conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.

13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a
work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey
the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special
requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will
apply to the combination as such.

14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time
to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new
problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the
GNU General Public License "or any later version" applies to it, you have the option of following the terms and
conditions either of that numbered version or of any later version published by the Free Software Foundation. If the
Program does not specify a version number of the GNU General Public License, you may choose any version ever
published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used,
that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the
Program.

Later license versions may give you additional or different permissions. However, no additional obligations are
imposed on any author or copyright holder as a result of your choosing to follow a later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT
WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 ix

16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE,
BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH
HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their
terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in
connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return
for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve
this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most
effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where
the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software: you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation, either version 3 of
the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If
not, see <http://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software,
and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License.
Of course, your program's commands might be different; for a GUI interface, you would use an "about box".

You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for
the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://
www.gnu.org/licenses/>.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your
program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first,
please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 x

Synopsys® license note: certain source files included with GNU Bison include the exception to the GPL-3.0 license
copied below.

As a special exception, you may create a larger work that contains part or all of the Bison parser skeleton and
distribute that work under terms of your choice, so long as that work isn't itself a parser generator using the
skeleton or a modified version thereof as a parser skeleton. Alternatively, if you modify or redistribute the parser
skeleton itself, you may (at your option) remove this special exception, which will cause the skeleton and the
resulting Bison output files to be licensed under the GNU General Public License without this special exception.

This special exception was added by the Free Software Foundation in version 2.2 of Bison.

Flex 2.5.37
Project homepage: http://flex.sourceforge.net/
Project license:

Flex carries the copyright used for BSD software, slightly modified because it originated at the Lawrence Berkeley (not
Livermore!) Laboratory, which operates under a contract with the Department of Energy:
Copyright © 2001, 2002, 2003, 2004, 2005, 2006, 2007 The Flex Project.
Copyright © 1990, 1997 The Regents of the University of California.
All rights reserved. This code is derived from software contributed to Berkeley by Vern Paxson.
The United States Government has rights in this work pursuant to contract no. DE-AC03-76SF00098 between the
United States Department of Energy and the University of California.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions
are met:
1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3.Neither the name of the University nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.

This basically says "do whatever you please with this software except remove this notice or take advantage of the
University's (or the flex authors') name".
Note that the "flex.skl" scanner skeleton carries no copyright notice.
You are free to do whatever you please with scanners generated using flex; for them, you are not even bound by the
above copyright.

LEF/DEF Reader 5.8-p008

Project homepage: http://projects.si2.org/openeda.si2.org/projects/lefdef
Project license:

Cadence LEF/DEF Agreement Version 2.1 January 17,2003

THE ACCOMPANYING SOFTWARE PROGRAM IS PROVIDED UNDER THE TERMS AND CONDITIONS OF THIS
LICENSE AGREEMENT ("AGREEMENT"). PLEASE REVIEW THIS AGREEMENT CAREFULLY. ANY USE,
REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES ACCEPTANCE OF
THIS AGREEMENT. IF YOU ARE AGREEING TO THIS LICENSE ON BEHALF OF A COMPANY, YOU REPRESENT
THAT YOU ARE AUTHORIZED TO BIND THE COMPANY TO THIS AGREEMENT.

Cadence Design Systems, Inc. (“Cadence”) is licensing the software program (“Program”) provided hereunder under
an open source arrangement. The licensee hereunder may use, copy and modify the Program only pursuant to this
Agreement. While Cadence encourages any and all improvements or other modifications made to the Program to be
contributed to the community source and thereby made available to others under the same terms and conditions as
included in this Agreement, this is not required. However, any error corrections made to the Program must be
contributed to the community source.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xi

1. DEFINITIONS

1.1 "Contribution" means the submission of the Original Program by Cadence and the submission of any
modifications, improvements, additions, corrections or other changes to the Program, including source code,
object code, application program interface definitions and formats, and documentation, made by any Contributor
where such changes and/or additions to the Program originate from and are distributed by that particular
Contributor. Each Contributor acknowledges and agrees that no guarantee is provided that a Contribution shall be
included within the Program as distributed by any Recipient. A Contribution must be made by a Contributor if; (1)
such Contribution is an error correction to the Program, or (2) the Contributor commercially distributes the
Program with such Contribution, in which case the Contribution must be made within thirty (30) days of the
commercial distribution of the Program. “Commercially distributes” as used herein shall mean distribution of the
Program by a Contributor in consideration for revenue received. A Contribution 'originates' from a Contributor if it
was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions
do not include additions to the Program which: (i) are separate modules of software or data distributed in
conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
1.2 "Contributor" means Cadence and any other entity that distributes the Program.
1.3 "Licensed Patents" mean patent claims licensable by any Contributor which are necessarily infringed by the use or
sale of its Contribution alone or when combined with the Program.
1.4 "Original Program" means the original version of the software accompanying this Agreement as released by
Cadence, including source code, object code, application program interface definitions and formats, and
documentation, if any.
1.5 "Program" means the Original Program and Contributions.
1.6 "Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

2.1 Subject to the terms and conditions of this Agreement, each Contributor hereby grants each Recipient a non-
exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display,
publicly perform, distribute and sublicense the Contribution of such Contributor, in source code and object code
format.
2.2 Subject to the terms and conditions of this Agreement, each Contributor hereby grants each Recipient a non-
exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import
and otherwise transfer the Contribution of such Contributor, if any, in source code and object code format along
with any documentation. This patent license shall apply to the combination of the Contribution and the Program if,
at the time the Contribution is added by the Contributor, such addition of the Contribution causes such
combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations
which include the Contribution.
2.3 Subject to the terms and conditions of this Agreement, Cadence hereby grants each Recipient a non-exclusive,
worldwide, royalty-free trademark license, to use the Cadence trademarks “LEF”, or “DEF”, in accordance with
Cadence’s marking policies, in connection with the license grants hereunder provided, however, that use of the
Cadence trademarks in connection with Recipient’s distribution of the Program is only permitted for the unmodified
Program.
2.4 Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no
assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual
property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any
other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the
rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other
intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient
to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
2.5 Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to
grant the copyright license set forth in this Agreement. Except as expressly stated in Sections 2.1, 2.2 and 2.3
above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this
Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly
granted under this Agreement are reserved.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xii

3. DISTRIBUTION REQUIREMENTS

3.1 A Contributor may choose to distribute the Program in object code form under its own license agreement, provided
that: (a) it complies with the terms and conditions of this Agreement; and (b) the terms and conditions of its license
agreement: (i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied,
including warranties or conditions of title and non-infringement, and implied warranties or conditions of
merchantability and fitness for a particular purpose; (ii) effectively excludes on behalf of all Contributors all liability
for damages, including, but not limited to, direct, indirect, special, incidental and consequential damages; (iii)
states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any
other party; and (iv) states that source code for the Program is available from such Contributor, and informs
licensees how to obtain it in a reasonable manner on or through a medium customarily used for software
exchange.
3.2 When the Program is made available in source code form it must be made available under the terms and
conditions of this Agreement. A copy of this Agreement must be included with each copy of such Program. A
Contributor may not charge a fee for the distribution of the source code of the Program.
3.3 Each Contributor must preserve all copyright and other notices that appear in the Program. In addition, each
Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows
subsequent Recipients to identify the originator of the Contribution.
3.4 While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the
Program in a commercial product offering should do so in a manner which does not create potential liability for
other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such
Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor
("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims,
lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused
by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a
commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any
actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a)
promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to
control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations.
The Indemnified Contributor may participate in any such claim at its own expense.

4. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for
determining the appropriateness of using and distributing the Program and assumes all risks associated with its
exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance
with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

5. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS
SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE
PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

6. GENERAL

6.1 If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or
enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto,
such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
6.2 If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software
(including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such
Recipient under this Agreement shall terminate as of the date such litigation is filed. If Recipient institutes patent
litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program
(excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s),
then such Recipient's rights granted under Section 2.2 shall terminate as of the date such litigation is filed.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xiii

6.3 If a Commercial Contributor distributes any Program, which includes such Contributors modifications,
improvements, additions, corrections or other changes, and has not made a Contribution of such Program, any
licenses granted to such Commercial Contributor under this Agreement shall terminate as of the date of such
Program is distributed.
6.4 All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or
conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware
of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use
and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this
Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
6.5 Cadence may publish new versions (including revisions) of this Agreement from time to time. Each new version of
the Agreement will be given a distinguishing version number. The Program (including Contributions) may always
be distributed subject to the version of the Agreement under which it was received. In addition, after a new version
of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under
the new version. No one other than Cadence has the right to modify this Agreement.
6.6 This Agreement is governed by the laws of the State of California and the intellectual property laws of the United
States of America. No party to this Agreement will bring a legal action under this Agreement more than one year
after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

END OF TERMS AND CONDITIONS

IN WITNESS WHEREOF, THE PARTIES HERETO HAVE ENTERED INTO THIS AGREEMENT AS OF THE
EFFECTIVE DATE.
RECIPIENT NAME:
___________________________________
Company Name if Corporate License
Signed by: __________________________
Name: _____________________________
Title: ______________________________
Mailing Address: ___________________
__________________________________
Phone Number: ____________________
e-mail address: ____________________

mcpp 2.7.2
Project homepage: http://sourceforge.net/projects/mcpp/
Project license:

Copyright © 1998, 2002-2008 Kiyoshi Matsui <[email protected]> All rights reserved.

This software including the files in this directory is provided under the following license.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xiv

Oasis Wrapper 1.0.0
Project homepage:
Project license:

The MIT License (MIT)

Copyright © 2015 Minhao Zhang

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Threading Building Blocks 4.4.0

Project homepage: https://www.threadingbuildingblocks.org/
Project license: https://www.threadingbuildingblocks.org/licensing

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991
Copyright © 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU
General Public License is intended to guarantee your freedom to share and change free software--to make sure the
software is free for all its users. This General Public License applies to most of the Free Software Foundation's
software and to any other program whose authors commit to using it. (Some other Free Software Foundation software
is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to
make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that
you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to
surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the
software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the
rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them
these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no
warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to
know that what they have is not the original, so that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors
of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we
have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xv

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it
may be distributed under the terms of this General Public License. The "Program", below, refers to any such program
or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that
is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into
another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is
addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
The act of running the Program is not restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running the Program). Whether that is
true depends on what the Program does.

1.You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium,
provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and
give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection
in exchange for a fee.

2.You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program,
and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet
all of these conditions:
a)You must cause the modified files to carry prominent notices stating that you changed the files and the date of any
change.
b)You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the
Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this
License.
c)If the modified program normally reads commands interactively when run, you must cause it, when started running
for such interactive use in the most ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users
may redistribute the program under these conditions, and telling the user how to view a copy of this License.
(Exception: if the Program itself is interactive but does not normally print such an announcement, your work based
on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from
the Program, and can be reasonably considered independent and separate works in themselves, then this License,
and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute
the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on
the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the
intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on
the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this
License.

3.You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you also do one of the following:
a)Accompany it with the complete corresponding machine-readable source code, which must be distributed under
the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b)Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than
your cost of physically performing source distribution, a complete machine-readable copy of the corresponding
source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for
software interchange; or,
c)Accompany it with the information you received as to the offer to distribute corresponding source code. (This
alternative is allowed only for noncommercial distribution and only if you received the program in object code or
executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable
work, complete source code means all the source code for all modules it contains, plus any associated interface

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xvi

 definition files, plus the scripts used to control compilation and installation of the executable. However, as a special
exception, the source code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering
equivalent access to copy the source code from the same place counts as distribution of the source code, even
though third parties are not compelled to copy the source along with the object code.

4.You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License.
Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate
your rights under this License. However, parties who have received copies, or rights, from you under this License will
not have their licenses terminated so long as such parties remain in full compliance.

5.You are not required to accept this License, since you have not signed it. However, nothing else grants you
permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do
not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you
indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.

6.Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a
license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You
may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to this License.

7.If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to
patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the
conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to
satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a
consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free
redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you
could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the
section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest
validity of any such claims; this section has the sole purpose of protecting the integrity of the free software
distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application of
that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system
and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8.If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted
interfaces, the original copyright holder who places the Program under this License may add an explicit geographical
distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9.The Free Software Foundation may publish revised and/or new versions of the General Public License from time to
time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new
problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and conditions either of that
version or of any later version published by the Free Software Foundation. If the Program does not specify a version
number of this License, you may choose any version ever published by the Free Software Foundation.

10.If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different,
write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to
the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software
generally.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xvii

NO WARRANTY

11.BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12.IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM
AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve
this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most
effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to
where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if
not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it under certain conditions; type
`show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License.
Of course, the commands you use may be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer"
for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program Gnomovision' (which makes
passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xviii

This General Public License does not permit incorporating your program into proprietary programs. If your program is
a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is
what you want to do, use the GNU Lesser General Public License instead of this License.

Runtime Exception:
As a special exception, you may use this file as part of a free software library without restriction. Specifically, if other
files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other
files to produce an executable, this file does not by itself cause the resulting executable to be covered by the GNU
General Public License. This exception does not however invalidate any other reasons why the executable file might
be covered by the GNU General Public License.

TCL/TK 8.5.12
Project homepage: https://www.tcl.tk/
Project license: https://www.tcl.tk/software/tcltk/license.html

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics
Corporation, ActiveState Corporation and other parties.

The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation
for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included
verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses.
Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described
here, provided that the new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,
OR MODIFICATIONS.

GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have
only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations
(FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the
software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted
Rights" as defined in Clause 252.227-7013 (b) (3) of DFARs. Notwithstanding the foregoing, the authors grant the U.S.
Government and others acting in its behalf permission to use and distribute the software in accordance with the terms
specified in this license.

zlib 12.5.3
Project homepage: http://www.zlib.net/
Project license: http://www.zlib.net/zlib_license.html

Copyright © 1995-2013 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for
any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it
and redistribute it freely, subject to the following restrictions:
1.The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you
use this software in a product, an acknowledgment in the product documentation would be appreciated but is not
required.
2.Altered source versions must be plainly marked as such, and must not be misrepresented as being the original
software.
3.This notice may not be removed or altered from any source distribution.

Jean-loup Gailly Mark Adler

[email protected] [email protected]

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xix

libedit
Project homepage: http://netbsd.org/
Project license:

Copyright © 1992, 1993 The Regents of the University of California. All rights reserved. This code is derived from
software contributed to Berkeley by Christos Zoulas of Cornell University.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3.All advertising materials mentioning features or use of this software must display the following acknowledgment:

This product includes software developed by the University of California, Berkeley and its contributors.

4.Neither the name of the University nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

IC Compiler™ II Library Preparation User Guide, Version M-2016.12-SP4 xx

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx

1. Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Reference Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Technology Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Frame-Only Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Aggregate Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Library Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Scaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Antenna Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Library Preparation Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Starting the Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Exiting the IC Compiler II Library Manager Tool . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Entering icc2_lm_shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Interrupting or Terminating Command Processing . . . . . . . . . . . . . . . . . . . . . . 1-12
Getting Information About Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Displaying Command Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Using Application Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

xxi
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Using Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Viewing Man Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Using Tcl Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Setup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Using the Command Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

2. Preparing Reference Libraries

Library Preparation Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Analyzing the Library Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Building Reference Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Defining the Search Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Creating a Library Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Specifying the Library Preparation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Specifying the Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Loading the Technology Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Completing the Technology Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Preparing Site Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Preparing Routing Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Loading the Logic Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Identifying the Process Associated With a Logic Library . . . . . . . . . . . . . . 2-16
Filtering Logic Libraries Based on Operating Corners . . . . . . . . . . . . . . . . 2-17
Loading Extracted Timing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Loading the Physical Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Reading LEF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Reading GDSII or OASIS Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Loading Physical Data from a Reference Library . . . . . . . . . . . . . . . . . . . . 2-30
Loading Physical Data from a Design Library. . . . . . . . . . . . . . . . . . . . . . . 2-31
Importing Milkyway FRAM Views From the IC Compiler Tool . . . . . . . . . . 2-32
Specifying Which Blocks to Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Handling Duplicate Blocks in the Physical Libraries . . . . . . . . . . . . . . . . . . . . . 2-33
Block Mapping File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Creating Scaling Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Loading Parasitic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Loading Signal Electromigration Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Completing the Physical Cell Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Preparing I/O Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Contents xxii
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Preparing Standard Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Preparing Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Querying the Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Validating the Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Library Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
PG Rail Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Cell Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Pin Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Timing Arc Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Scaling Group Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Leakage-Power Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Allowing Incomplete or Inconsistent Library Data . . . . . . . . . . . . . . . . . . . . . . . 2-53
Creating a Mismatch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Setting a Mismatch Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Reporting Mismatch Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Generating Frame Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Identifying Secondary PG Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Committing the Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61
Using the Exploration Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Enabling Scaling Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Performing Automated Library Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Using a Library Preparation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Using the Fast Exploration Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Verifying Reference Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Verifying Logical Information in a Reference Library . . . . . . . . . . . . . . . . . . . . . 2-68
Verifying the Frame Views in a Reference Library. . . . . . . . . . . . . . . . . . . . . . . 2-69
Modifying a Reference Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Defining Antenna Properties on Standard Cells . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Antenna Properties for Standard Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
Defining Antenna Properties on Hard Macro Cells . . . . . . . . . . . . . . . . . . . . . . 2-73
Antenna Properties for Hard Macro Cells . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
Creating an Aggregate Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
Setting the Search Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
Modifying an Aggregate Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
Opening a Reference Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
Getting Information About Reference Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78

Chapter 1: Contents
Contents xxiii
1-xxiii
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Querying Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79

Reporting Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79
Reporting the Frame Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82
Querying Library Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83
Reporting Library Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84
Exporting Reference Library Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86
Closing a Reference Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87

Appendix A. Library Manager Application Options

Library Manager Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
LEF Input Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
GDSII and OASIS Input Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Timing View Generation Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Frame View Generation Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Antenna Extraction Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Command-Line Interface Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
Graphical User Interface Application Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19

Appendix B. Working With the Library Manager GUI

Starting the Tool in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Opening the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Closing the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Exiting the Tool From the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Using the Library Preparation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Creating a Reference Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Modifying a Reference Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Viewing a Reference Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Working in the Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
Using the Library Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
Using the Message Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Contents xxiv
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Appendix C. Using Non-PG Logic Libraries

PG Rail Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
PG Pin Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Chapter 1: Contents
Contents xxv
1-xxv
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Contents xxvi
Preface
This preface includes the following topics:
• About This Guide
• Customer Support

xxvii
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

About This Guide

The IC Compiler II Library Manager tool merges input from a variety of sources to create a
single, unified reference library that contains all of the physical and logical information for a
technology and its library cells. Reference libraries created by the IC Compiler II Library
Manager tool are used by the IC Compiler II tool to implement designs.

Audience
This user guide is for engineers who use the IC Compiler II Library Manager tool to prepare
libraries for use with the IC Compiler II tool.
To use the IC Compiler II Library Manager tool, you need to be familiar with the following:
• Logical and physical design principles
• The Linux or UNIX operating system
• The tool command language (Tcl)

Related Publications
For additional information about the IC Compiler II Library Manager tool, see the
®
documentation on the Synopsys SolvNet online support site at the following address:
https://solvnet.synopsys.com/DocsOnWeb
You might also want to see the documentation for the following related Synopsys products:
• Library Compiler™
• IC Compiler™ II

Release Notes
Information about new features, enhancements, changes, known limitations, and resolved
Synopsys Technical Action Requests (STARs) is available in the IC Compiler II Release
Notes on the SolvNet site.
To see the IC Compiler II Release Notes,
1. Go to the SolvNet Download Center located at the following address:
https://solvnet.synopsys.com/DownloadCenter
2. Select IC Compiler II, and then select a release in the list that appears.

Preface
About This Guide xxviii
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Conventions
The following conventions are used in Synopsys documentation.

Convention Description

Courier Indicates syntax, such as write_file.

Courier italic Indicates a user-defined value in syntax, such as

write_file design_list.

Courier bold Indicates user input—text you type verbatim—in

examples, such as
prompt> write_file top

[] Denotes optional arguments in syntax, such as

write_file [-format fmt]

... Indicates that arguments can be repeated as many

times as needed, such as
pin1 pin2 ... pinN

| Indicates a choice among alternatives, such as

low | medium | high

Control-c Indicates a keyboard combination, such as holding

down the Control key and pressing c.

\ Indicates a continuation of a command line.

/ Indicates levels of directory structure.

Edit > Copy Indicates a path to a menu command, such as

opening the Edit menu and choosing Copy.

Preface 1: Preface
Chapter
About This Guide 1-xxix
xxix
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Customer Support
Customer support is available through SolvNet online customer support and through
contacting the Synopsys Technical Support Center.

Accessing SolvNet
The SolvNet site includes a knowledge base of technical articles and answers to frequently
asked questions about Synopsys tools. The SolvNet site also gives you access to a wide
range of Synopsys online services including software downloads, documentation, and
technical support.
To access the SolvNet site, go to the following address:
https://solvnet.synopsys.com
If prompted, enter your user name and password. If you do not have a Synopsys user name
and password, follow the instructions to sign up for an account.
If you need help using the SolvNet site, click HELP in the top-right menu bar.

Contacting the Synopsys Technical Support Center

If you have problems, questions, or suggestions, you can contact the Synopsys Technical
Support Center in the following ways:
• Open a support case to your local support center online by signing in to the SolvNet site
at https://solvnet.synopsys.com, clicking Support, and then clicking “Open A Support
Case.”
• Send an e-mail message to your local support center.
❍ E-mail [email protected] from within North America.
❍ Find other local support center e-mail addresses at
http://www.synopsys.com/Support/GlobalSupportCenters/Pages
• Telephone your local support center.
❍ Call (800) 245-8005 from within North America.
❍ Find other local support center telephone numbers at
http://www.synopsys.com/Support/GlobalSupportCenters/Pages

Preface
Customer Support xxx
1
Working With the IC Compiler II Library
Manager Tool 1
You use the IC Compiler II Library Manager tool to build a reference library for use with the
IC Compiler II implementation tool. To learn how to use the library manager, see the
following topics:
• Library Preparation Terminology
• Library Preparation Flow
• User Interfaces
• Entering icc2_lm_shell Commands
• Using Application Options
• Using Variables
• Viewing Man Pages
• Using Tcl Scripts
• Setup Files
• Using the Command Log File

1-1
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Library Preparation Terminology

The following terms are used to describe the library preparation process for the IC Compiler
II tool:
• Reference Library
• Technology Library
• Frame-Only Library
• Aggregate Library
• Library Workspace
• Pane
• Breakpoints
• Scaling Group
• Antenna Properties

Reference Library
Reference libraries for the IC Compiler II tool use the new data model (NDM) format. These
reference libraries are unified libraries that contain the logical and physical information for a
specific technology and one or more of its library cells. Each library cell is represented as a
single object with multiple views that contain various types of information about the cell. A
library cell can have the following views:
• Timing view
The timing view contains the timing, power, and functional information for a cell. It should
contain timing and power information for all necessary characterization points (voltage
and temperature) for a given process setting. The data for each characterization point is
stored in a pane.
The IC Compiler II tool uses the timing view to perform static timing analysis, power
analysis, and optimization.
• Layout view
The layout view contains the physical shape information for a cell, not including
connectivity and pins.
The library manager uses the layout view to create the design view from GDSII or Open
Artwork System Interchange Standard (OASIS) source libraries, and the IC Compiler II
tool uses it for mask generation.

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-2
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

• Design view
The design view contains the physical shape information for a cell, including connectivity
and pins.
The library manager uses the design view to create the frame view.
• Frame view
The frame view contains the information needed to perform placement and routing, such
as the block boundary, pins, via regions, and routing blockages.
The IC Compiler II tool uses the frame view to perform placement and routing.

Figure 1-1 shows a conceptual view of a reference library. The views shown in green are the
views used by the IC Compiler II tool.
Figure 1-1 Conceptual View of a Reference Library

You create a reference library by loading the logical and physical models from the following
sources:
• The technology file
The technology file contains information about the routing layers and routing rules for a
specific technology.
The IC Compiler II tool uses the same technology file as the IC Compiler tool. For
information about the technology file syntax, see the Synopsys Technology File and
Routing Rules Reference Manual.
• The logic libraries
The source files for the logic libraries are Liberty libraries in compiled (.db) format. These
files contain the timing, power, and functionality information for the library cells (standard

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-3
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

cells or macro cells). Each file represents a characterization point for a specific process,
voltage, and temperature.
Note:
This book assumes that the logic libraries use the power and ground (PG) pin syntax.
For information about using older logic libraries that use the rail_connection
attribute to define the PG pin connections or do not define the PG pins, see Appendix
C, “Using Non-PG Logic Libraries.”
• The physical libraries
The source files for the physical libraries are Library Exchange Format (LEF) files, GDSII
files, OASIS files, existing reference libraries in NDM format, or the FRAM views
exported from the IC Compiler tool. These files contain the physical shape data for the
library cells.
• TLUPlus files (optional)
The TLUPlus files contain the RC coefficients for a specific technology. The TLUPlus
models enable accurate RC extraction results by including the effects of width, space,
density, and temperature on the resistance and capacitance.
You can store the TLUPlus information either in the reference library or in the design
library. For information about storing TLUPlus information in a design library, see the
IC Compiler II Implementation User Guide.

A reference library contains all of the required information, both logical and physical, for a
set of cells for a technology. The IC Compiler II tool does not directly use the source files
used to generate a reference library.

See Also
• Preparing Reference Libraries

Technology Library
A technology library is a reference library that contains only the information from the
technology file and TLUPlus files. It does not contain any library cells.

See Also
• Reference Library

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-4
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Frame-Only Library
A frame-only library is an intermediate library that contains only physical information (frame,
design, and layout views) for the library cells. This type of reference library is used only as
an input to generate a reference library; it cannot be used outside of the library manager.

See Also
• Reference Library

Aggregate Library
An aggregate library combines multiple reference libraries into a single reference library with
a defined search order for the included reference libraries. When you refer to a cell in an
aggregate library, the tool uses the defined search order to find the first occurrence of the
cell. You can use an aggregate library to group related reference libraries for easier
maintenance and distribution.

See Also
• Creating an Aggregate Library

Library Workspace
A library workspace is the in-memory representation of a reference library while it is being
built. You use a library workspace to create a new reference library, modify an existing
reference library, or create an aggregate reference library. You load the source files into the
library workspace, validate the contents, and then commit the workspace to save it as a
reference library.
There are two types of library workspaces:
• Root workspace
This is the main library workspace. Only a single root workspace can be open at one
time. If you are creating a single reference library, you work only with a root workspace.
• Subworkspaces
Subworkspaces are used in the exploration flow to partition source data into multiple
reference libraries. Each subworkspace generates a single reference library.

See Also
• Creating a Library Workspace

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-5
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Pane
A pane is the representation of the timing and power data for a cell. In general, a pane
represents the data at a single characterization point (temperature and voltage) for a given
process setting. In some cases, the data for multiple characterization points at the same
process setting can be merged into a single pane, which is called a scaling group.
If you are not using scaling groups, the timing view of a cell contains a pane for each logic
library that contains that cell. Each pane is indexed by its voltage and temperature values.

See Also
• Scaling Group

Breakpoints
In a logic library, a timing arc is represented as a lookup table. The index values specified in
the lookup table are referred to as the breakpoints for the timing arc. During timing analysis,
the tool uses interpolation to determine the timing values for points between the specified
breakpoints.

See Also
• Timing Arc Checks

Scaling Group
For a given process, you might have multiple logic libraries that represent different
characterization points (voltage and temperature). By default, timing analysis is performed
only at these characterization points. If the characterization points for a set of logic libraries
form a complete grid, you can create a scaling group, which merges the characterization
points into a single pane. A pane that represents a single logic library uses the indexes
specified in the logic library for the timing arc, typically input slew and output capacitance. A
pane that represents a scaling group has indexes for voltage, temperature, or both, in
addition to the indexes specified in the logic library. These higher-dimension delay tables
enable very efficient delay calculations in the IC Compiler II tool. In addition, they enable
interpolation between the voltage and temperature values of the characterization points,
which enables efficient multivoltage analysis and optimization.
The characterization points form a complete grid when data exists for each temperature and
voltage combination. Figure 1-2 shows an example of a complete grid and an incomplete
grid. The figure on the left represents a complete grid that consists of four logic libraries for
a process. The figure on the right represents an incomplete grid that consists of three logic

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-6
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

libraries for a process. The grid is incomplete because the characterization point at 1.0V and
0°C is missing.
Figure 1-2 Grid Representation of Characterization Points

Complete grid Incomplete grid

See Also
• Creating Scaling Groups

Antenna Properties
MOS transistor gate oxides are easily damaged by electrostatic discharge, especially during
the manufacturing process. The static charge collected on lower-level wires during
multilevel metalization processing can destroy gate oxides and ruin the chip. This issue is
called the “antenna problem.”
To protect the MOS device from being damaged, the area of the metal connected to a gate
oxide during a given metal mask stage must be limited to a certain value. When the metal
area exceeds this value, a reverse-biased diode can be used to provide a discharge path to
protect the gate oxide at a cell input.
The diffusion areas of output pins provide protection for gate oxides at input pins. However,
at intermediate stages of the manufacturing process, unconnected metal wires extending
from the input pins can cause antenna problems to occur. For many process technologies,
antenna properties specify the maximum ratio of antenna area (the metal area of dangling
connections) to gate area (the gate area of input pins). This ratio can be a constant value or
a value derived by an antenna equation.

See Also
• Automatic Antenna Property Extraction Using the IC Validator Tool
• Defining Antenna Properties on Standard Cells
• Defining Antenna Properties on Hard Macro Cells

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Terminology 1-7
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Library Preparation Flow

Figure 1-3 shows the library preparation flow used to build a reference library.
Figure 1-3 Library Preparation Flow

For detailed information about the library preparation flow, see “Preparing Reference
Libraries.”

Chapter 1: Working With the IC Compiler II Library Manager Tool

Library Preparation Flow 1-8
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

User Interfaces
The IC Compiler II Library Manager tool operates in the X windows environment on UNIX or
Linux. It provides a flexible working environment with both a shell command-line interface
and a graphical user interface (GUI).
• The shell command-line interface, icc2_lm_shell, is a text-only environment in which you
enter commands at the command-line prompt. It is typically used for scripts, batch mode,
and push-button operations and is always available during a library manager session.
• The GUI provides a wizard to perform library preparation, as well as tools for viewing and
editing the cells in your library. The look and feel of the library manager GUI is consistent
with the look and feel of other Synopsys GUIs.

The library manager uses the tool command language (Tcl). Using Tcl, you can extend the
icc2_lm_shell command language by writing reusable procedures and scripts (see the
Using Tcl With Synopsys Tools manual).
You can start or exit a session in either icc2_lm_shell or the GUI, and you can open or close
the GUI at any time during a session. The following topics describe how to start and exit the
tool using the command-line interface:
• Starting the Command-Line Interface
• Exiting the IC Compiler II Library Manager Tool

See Also
• Working With the Library Manager GUI

Chapter 1: Working With the IC Compiler II Library Manager Tool

User Interfaces 1-9
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Starting the Command-Line Interface

To start the icc2_lm_shell command-line interface,
1. Include the path to the bin directory in your $PATH variable.
2. Enter the icc2_lm_shell command in a UNIX or Linux shell.
% icc2_lm_shell

You can include other options when you start icc2_lm_shell. For example,
❍ -file script_file_name to execute a script

❍ -x command to execute an icc2_lm_shell command

❍ -output_log_file file_name to create a log file of your session

❍ -h to display a list of the available options (without starting icc2_lm_shell)

At startup, icc2_lm_shell performs the following tasks:

1. Creates a command log file.
2. Reads and executes the setup files.
3. Executes any script files or commands specified by the -f and -x options, respectively,
on the command line.
4. Displays the program header and icc2_lm_shell> prompt in the shell.

See Also
• Starting the Tool in the GUI
• Using the Command Log File
• Setup Files
• Using Tcl Scripts

Chapter 1: Working With the IC Compiler II Library Manager Tool

User Interfaces 1-10
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Exiting the IC Compiler II Library Manager Tool

To exit the IC Compiler II Library Manager tool, use the exit or quit command.
Note:
When you exit the tool from the command line, the tool exits without saving the open
library workspace.

See Also
• Exiting the Tool From the GUI

Entering icc2_lm_shell Commands

You interact with the library manager by using icc2_lm_shell commands, which are based
on the tool command language (Tcl) and include certain command extensions needed to
implement specific IC Compiler II Library Manager functionality. The library manager
command language provides capabilities similar to UNIX command shells, including
variables, conditional execution of commands, and control flow commands. You can
• Enter individual commands interactively at the icc2_lm_shell> prompt
• Enter individual commands interactively on the console command line in the GUI
• Run one or more Tcl scripts, which are text files that contain icc2_lm_shell commands

When entering a command, an option, or a file name, you can minimize your typing by
pressing the Tab key. If you have typed enough characters to specify a unique name, the
IC Compiler II library manager completes the remaining characters. If the characters you
typed can be used for more than one name, the library manager lists the qualifying names,
from which you can select by using the arrow keys and the Enter key.
If you need to reuse a command from the output for a command-line interface, you can copy
and paste the portion by selecting it, moving the pointer to the icc2_lm_shell command line,
and clicking with the middle mouse button.
When you run a command, the library manager echoes the command output (including
processing messages and any warnings or error messages) in icc2_lm_shell and, if the GUI
is open, in the console log view. By default, the output scrolls. To prevent scrolling, enable
page mode by setting the sh_enable_page_mode variable to true.

See Also
• Using Tcl Scripts

Chapter 1: Working With the IC Compiler II Library Manager Tool

Entering icc2_lm_shell Commands 1-11
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Interrupting or Terminating Command Processing

To interrupt command processing and remain in icc2_lm_shell, press Ctrl+C.
When you use Ctrl+C, keep the following points in mind:
• If a script file is being processed and you interrupt one of its commands, the script
processing is interrupted and no further script commands are processed.
• If you press Ctrl+C three times before a command responds to your interrupt,
icc2_lm_shell is interrupted and exits with this message:
Information: Process terminated by interrupt.

Some commands and processes cannot be interrupted. To stop these commands or

processes, you must terminate icc2_lm_shell at the system level. When you terminate a
process or the shell, data is not saved.

Getting Information About Commands

The following online information resources are available while you are using the IC Compiler
II library manager:
• Command help
• Command man pages

Displaying Command Help

Command help consists of either a brief description of an icc2_lm_shell command or a list
of the options and arguments supported by an icc2_lm_shell command.
• To display a brief description of a command, enter the help command followed by the
command name. For example, to display a brief description of the read_db command,
use the following command:
icc2_lm_shell> help read_db

• To display the options supported by an icc2_lm_shell command, enter the command

name with the -help option. For example, to see the options supported by the
create_workspace command, use the following command:
icc2_lm_shell> read_db -help

Chapter 1: Working With the IC Compiler II Library Manager Tool

Entering icc2_lm_shell Commands 1-12
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Using Application Options

The IC Compiler II Library Manager tool uses application options to control the tool behavior.
Application options use the following naming convention:
category[.subcategory].option_name

where category is the name of the tool feature affected by the application option. Some
application option categories have subcategories to further refine the area affected by the
application option.
You use the following commands to work with application options:
• set_app_options: Sets one or more application options.

• reset_app_options: Resets one or more application options so that they have no value

• get_app_options: Lists the available application options.

• get_app_option_value: Reports the setting for a specific application option.

• report_app_options: Reports application options and their settings.

For more information about working with application options, see the IC Compiler II Data
Model User Guide.

Using Variables
In general, the library manager modifies default behavior by using application options rather
than application variables; however it does support user-defined Tcl variables, as well as a
minimal number of application variables, such as the search_path variable.

See Also
• Defining the Search Path
• Using Application Options

Chapter 1: Working With the IC Compiler II Library Manager Tool

Using Application Options 1-13
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Viewing Man Pages

To display the man page for an icc2_lm_shell command or application variable, enter the
man command followed by the command or variable name. For example, to see the man
page for the read_db command, use the following command:
icc2_lm_shell> man read_db

To display the man page for an icc2_lm_shell application option, enter the man command
followed by the option name. You can also view the following types of summary pages for
application options:
• Category summaries
To view a man page the summarizes all of the application options for a specific category,
enter the man command followed by category_options. For example, to see the man
page that summarizes all library manager application options, use the following
command:
icc2_lm_shell> man lm_options

• Subcategory summaries
To view a man page the summarizes all of the application options for a specific
subcategory, enter the man command followed by category.subcategory_options. For
example, to see the man page that summarizes all signoff antenna extraction application
options, use the following command:
icc2_lm_shell> man signoff.antenna_options

• Command summaries
To view a man page the summarizes all of the application options for a specific
command, enter the man command followed by command_options. For example, to see
the man page that summarizes all application options that affect the read_db command,
use the following command:
icc2_lm_shell> man read_db_options

If you enter the man command on the icc2_lm_shell command line, the man page is
displayed in the shell and in the console log view if the GUI is open. If you enter this
command on the console command line in the GUI, the man page is displayed in the GUI
man page viewer.

See Also
• IC Compiler II Graphical User Interface User Guide

Chapter 1: Working With the IC Compiler II Library Manager Tool

Viewing Man Pages 1-14
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Using Tcl Scripts

You can use Tcl scripts to accomplish routine, repetitive, or complex tasks.
A Tcl script is a text file that contains a sequence of any icc2_lm_shell commands. It can
also include comments, which are indicated by a pound sign (#) at the beginning of a line.
# This is a comment

You can use the following methods to run a Tcl script:

• To run a script from the command line, use the source command.
• To run a script in the GUI, choose File > Execute Script.
• To run a script when you start the tool, use the -f option with the icc2_lm_shell
command.
If an error occurs when running a command in the script, the library manager raises the
TCL_ERROR condition, which immediately stops the script execution. To tolerate errors
and allow the script to continue executing, either
• Check for TCL_ERROR error conditions with the Tcl catch command on the commands
that might generate errors.
• Set the sh_continue_on_error variable to true in the script file.

See Also
• Starting the Command-Line Interface
• Using Tcl With Synopsys Tools

Chapter 1: Working With the IC Compiler II Library Manager Tool

Using Tcl Scripts 1-15
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Setup Files
A setup file is a special Tcl script that the tool automatically executes at startup. It can
contain commands that perform basic tasks, such as initializing application options.
The setup file for the library manager is named .synopsys_icc2_lm.setup. The tool looks for
this file both in your home directory and in the project directory (the current working directory
in which you start the tool). The file is read in the following order:
1. The .synopsys_icc2_lm.setup file in your home directory
Typically the settings in this file define your working environment.
2. The .synopsys_icc2_lm.setup file in the project directory
Typically the settings in this file affect the processing of a specific library.

See Also
• User Interfaces
• Using Application Options
• Using Variables
• Using Tcl Scripts

Using the Command Log File

The command log file records the icc2_lm_shell commands processed by the library
manager, including setup file commands and application option settings. By default, the tool
writes the command log to a file named icc2_lm_command.log in the working directory.
To change the name of the command log file, set the sh_command_log_file variable in
your .synopsys_icc2_lm.setup file. If your user-defined or project-specific setup file does not
contain this variable, the tool automatically creates the icc2_lm_command.log file.
Each session overwrites the existing command log file. To save a command log file, move it
or rename it. You can use the command log file to
• Record the library preparation process
• Document any problems in the current session

See Also
• Setup Files

Chapter 1: Working With the IC Compiler II Library Manager Tool

Setup Files 1-16
2
Preparing Reference Libraries 2
To learn how to prepare reference libraries for the IC Compiler II tool, see the following
topics:
• Library Preparation Flows
• Analyzing the Library Source Files
• Building Reference Libraries
• Using the Exploration Flow
• Verifying Reference Libraries
• Modifying a Reference Library
• Creating an Aggregate Library
• Modifying an Aggregate Library
• Opening a Reference Library
• Getting Information About Reference Libraries
• Exporting Reference Library Content
• Closing a Reference Library

2-1
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Library Preparation Flows

The library manager supports the following library preparation flows:
• Normal flow
Use this flow to create a reference library if you have a single logic library file or a group
of logic library files, each of which contains the same set of cells but has timing data for
a different characterization point, and physical library files that contain a superset of the
cells in the logic library files. Library vendors typically use this library organization for
standard cells and pad cells.
By default, the generated reference library contains the cells that exist in both the logic
and physical library files. It contains both logical information (timing views) and physical
information (frame, design, and layout views) for these cells.
• Technology-only flow
Use this flow to create a reference library that contains only the information from the
technology file and TLUPlus files. This type of reference library is referred to as a
technology library.
• Frame-only flow
Use this flow to create an intermediate library that contains only the physical information
for the cells. This type of reference library is referred to as a frame-only library. It is used
only as an input to the library preparation process.
For this flow, you either read only the physical libraries or both the physical and logic
libraries. If you read both the physical and logic libraries, the tool uses the logic libraries
only to determine the port direction when conflicts occur.
The generated library contains the cells that exist in the physical library files. It contains
only the physical information (frame, design, and layout views) of these cells.
• Extracted timing model (ETM) flow
Use this flow to create a reference library if you have several extracted timing models,
each of which represents a single mode and characterization point for the same design,
and a physical library file that contains the design.
The generated reference library contains the design represented by the extracted timing
model, assuming that physical information is provided for that design. If the physical
library files contain additional designs, they are not included in the generated reference
library.
• Physical-only flow
Use this flow to create a separate physical-only reference library for the cells that exist
only in a physical library file and do not exist in any of the logic library files. A

Chapter 2: Preparing Reference Libraries

Library Preparation Flows 2-2
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

physical-only library typically contains cells such as filler cells, tap cells, flip-chip pad
cells, endcap cells, and decoupling capacitor cells.
The group of files used for this flow includes all of the logic and physical library files;
however, the generated reference library includes only those cells that exist only in the
physical library files.
Note:
You must read at least one logic library when using the physical-only flow; otherwise,
workspace validation fails and you cannot save the reference library. To build a library
of cells using only physical libraries, use the frame-only flow.
• Exploration flow
Use this flow to automatically analyze the library source files and generate a script that
you can use to create a reference library.
• Edit flow
Use this flow to modify the physical data for cells in an existing reference library.
• Aggregate flow
Use this flow to combine multiple separate reference libraries into a single reference
library.

Figure 2-1 shows the results of using the normal and physical-only flows on a library
workspace that contains two .db files, each of which contains a different characterization
point for the same set of cells, and one LEF file.

Chapter 2: Preparing Reference Libraries

Library Preparation Flows 2-3
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Figure 2-1 Normal and Physical-Only Example

See Also
• Reference Library
• Technology Library

Analyzing the Library Source Files

Note:
This topic describes the manual process for analyzing the library source files. You can
use the exploration flow to perform this task automatically; however, you should read this
topic to understand the analysis process. For information about using the exploration
flow to perform this task, see Using the Exploration Flow.
Before you build the reference libraries, you must analyze your library source files to
determine which library preparation flow to use. Depending on your library source files, you
might create several reference libraries using various library preparation flows. When you
build multiple reference libraries, you need to determine which source files to use for each
reference library.

Chapter 2: Preparing Reference Libraries

Analyzing the Library Source Files 2-4
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

When grouping the library source files, consider the following:

• In general, each cell should be included in both a logic library file and a physical library
file.
The logic library file provides the information for the timing view, while the physical library
file provides the information for the layout, design, and frame views.
• If you load multiple logic library files into a library workspace, they must all represent the
same process. In addition, the logic library files must meet one of the following
conditions:
❍ All the logic library files contain the same set of cells but each one provides data for
a different temperature and voltage point.
❍ Each logic library file contains only a single cell; if the files contain different cells, the
group must include a logic library file for each cell at each temperature and voltage
point.
• Each cell should exist in only one group, and that group should contain cell data for all
necessary temperature and voltage corners.
Warning:
If multiple reference libraries contain a library cell with the same name, the tool uses
the data from the first reference library in which it finds the cell, and it ignores that
cell’s data in all other reference libraries. This phenomenon is referred to as cell
shadowing.
• A physical library file might belong to several groups, because it might contain more cells
than any single logic library file.
You should ensure that all cells in the physical library files are included in a reference
library. Ideally, each cell is included in exactly one reference library; otherwise, users
must be very careful when specifying the reference library order for a design library. If a
physical library file contains cells that do not exist in any of the logic library files, these
cells are considered physical-only cells. You should create a separate reference library
for these physical-only cells.

See Also
• Reference Library

Chapter 2: Preparing Reference Libraries

Analyzing the Library Source Files 2-5
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Building Reference Libraries

The basic process for building a reference library is the same regardless of the library
preparation flow you choose. The only differences are the options that you use when
creating the library workspace and the library source files that you load into the workspace.
The following figure shows an overview of the library preparation process. For detailed
information about a task, click on the task in the figure.
Figure 2-2 Overview of the Library Preparation Process

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-6
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

To build a technology library, you follow the same flow, but omit steps four through seven,
which involve the source files for the library cells.
After a reference library is built, it does not need to be rebuilt unless one of the source library
files changes or a new version of the IC Compiler II tool requires an updated library.

See Also
• Using the Exploration Flow
• Modifying a Reference Library
• Creating an Aggregate Library

Defining the Search Path

The library manager uses a search path to look for files that are specified with a relative path
or no path.
To specify the search path, set the search_path application variable to the list of
directories, in order, in which to look for files. When the library manager looks for a file, it
starts searching in the leftmost directory specified in the search_path variable and uses the
first matching file it finds.

Creating a Library Workspace

To create a library workspace, use the create_workspace command. When you run this
command to create a new reference library, you must specify the following items:
• The name of the workspace
For all flows except the edit flow, specify the workspace name without a file extension.
For the edit flow, specify the name of an existing reference library, including its .ndm file
extension.
• The library preparation flow you are using
By default, the tool creates a workspace for the normal library preparation flow. To
specify a different flow, use the -flow option, as described in Specifying the Library
Preparation Flow.
Note:
The create_workspace command fails if there are any reference libraries in memory.
Before running the create_workspace command, use the close_lib command to
close any open libraries.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-7
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

For example, to use the normal flow to create a reference library named myreflib, use the
following command to create the library workspace:
icc2_lm_shell> create_workspace myreflib

You can optionally specify the following items:

• The technology data for the library
To provide the technology data when you create the library workspace, use one of the
following methods:
❍ Load a technology file by using the -technology option. This is the preferred method
for providing the technology data.
❍ Reference a technology library by using the -use_technology_lib option.
For more information, see Loading the Technology Data.
• The scale factor for the library
The scale factor specifies the number of database units per micron. The default scale
factor is 10000, which means that each database unit represents 1 Angstrom. However,
the recommended scale factor is the technology length precision as specified by the
lengthPrecision attribute in the technology file. To use the technology length precision
as the scale factor, set the lib.setting.use_tech_scale_factor application option to
true before running the create_workspace command.
For more information about setting the scale factor, see Specifying the Scale Factor.

See Also
• Library Workspace
• Analyzing the Library Source Files
• Using the Exploration Flow
• Modifying a Reference Library
• Creating an Aggregate Library

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-8
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Specifying the Library Preparation Flow

By default, the create_workspace command creates a library workspace for the normal
flow. To create a library workspace for a different library preparation flow, use the -flow
option to specify the flow. Table 2-1 shows the options to use for the supported library
preparation flows.
Table 2-1 create_workspace Options To Specify the Library Preparation Flow

Library preparation flow create_workspace -flow keyword

Reference library creation flows

Normal normal

Technology-only normal

Frame-only frame

Extracted timing model etm_moded

Physical-only physical_only

Exploration exploration

Reference library verification flow

Verification verification

Reference library modification flow

Edit edit

Aggregate library creation flow

Aggregate aggregate

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-9
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

For example, to use the normal flow to create a reference library named myreflib, use the
following command:
icc2_lm_shell> create_workspace myreflib

To use the physical-only flow to create a reference library named myreflib_po, use the
following command:
icc2_lm_shell> create_workspace -flow physical_only myreflib_po

To create a workspace for the exploration flow, use the following command:
icc2_lm_shell> create_workspace -flow exploration myreflib_explore

Note:
Unless you are using the exploration flow, you can have only one library workspace open
at a time. To remove the current library workspace from memory without committing it to
a saved reference library, use the remove_workspace command.

See Also
• Library Workspace
• Analyzing the Library Source Files
• Using the Exploration Flow
• Verifying Reference Libraries
• Modifying a Reference Library
• Creating an Aggregate Library

Specifying the Scale Factor

The scale factor specifies the number of database units per micron. The IC Compiler II tool
uses the scale factor to convert floating point numbers into integers when storing data in the
reference libraries and design libraries. When the tool saves a floating point number, it
multiplies the number by the scale factor and then rounds the number to an integer. When

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-10
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

the tool retrieves the number, it divides the number by the scale factor. For example, if the
scale factor is 1000, the tool stores a value of 0.0032 as 3 (0.0032 * 1000 = 3.2, which
rounds to 3). The tool retrieves this value as 0.003 (3 / 1000).
If the scale factor is not large enough, the precision of specified coordinates might be
affected. For example, assume that you create a net shape with the following command:
icc2_shell> create_shape -shape_type rect -layer M1 \
-boundary {{0.500 0.500} {0.5053 0.5053}}

With a scale factor of 1000, the bounding box is stored as {500 500} {505 505}, instead of
{5000 5000} {5053 5053}. With a scale factor of 10000, the bounding box is stored as {5000
5000} {5053 5053}.
The scale factor for a library workspace must be a multiple of both the length precision of the
technology file associated with the workspace and the scale factor of the physical libraries
loaded into the workspace.
The default scale factor is 10000, which means that each database unit represents 1
Angstrom. However, the recommended scale factor is the technology length precision as
specified by the lengthPrecision attribute in the technology file. To use the technology
length precision as the scale factor, set the lib.setting.use_tech_scale_factor
application option to true before running the create_workspace command.
icc2_lm_shell> set_app_options \
-name lib.setting.use_tech_scale_factor -value true

If neither the default scale factor nor the technology length precision is appropriate for your
library, you can explicitly specify the scale factor by using the -scale_factor option with
the create_workspace command.
To determine the scale factor for an existing reference library, query its scale_factor
attribute.

Loading the Technology Data

You can load the technology data for a reference library either by reading a technology file
into the library workspace, which is the preferred method, or by associating a technology
library with the library workspace.
• To load a technology file into a library workspace when you create the workspace, use
the -technology option with the create_workspace command.
For example, to use the normal flow to create a reference library named myreflib that
gets its technology data from the my.tf technology file, use the following command:
icc2_lm_shell> create_workspace -technology my.tf myreflib

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-11
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• To load a technology file into an existing library workspace, use the read_tech_file
command.
For example, to load the my.tf technology file into the current library workspace, use the
following command:
icc2_lm_shell> read_tech_file my.tf

• To associate a technology library with a library workspace when you create the
workspace, use the -use_technology_lib option with the create_workspace
command.
For example, to use the normal flow to create a reference library named myreflib that
gets its technology data from the mytech.ndm technology library, use the following
command:
icc2_lm_shell> create_workspace -use_technology_lib mytech.ndm \
myreflib

• To associate a technology library with an existing library workspace, use the read_ndm
command to read the technology library into the library workspace.
For example, to associate the mytech.ndm technology library with the current library
workspace, use the following command:
icc2_lm_shell> read_ndm mytech.ndm

When you load technology data into an existing library workspace,

• The new technology data overwrites any existing technology data, whether from a
previous technology file or specified with Tcl commands
• The library manager verifies that the frame views in the library workspace are consistent
with the new technology data
Important:
The technology file does not contain all of the technology data required to perform
placement and routing in the IC Compiler II tool. For information about completing the
technology data, see Completing the Technology Data.

See Also
• Creating a Library Workspace
• “Technology Data Access” in the IC Compiler II Data Model User Guide

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-12
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Completing the Technology Data

The technology file does not contain all of the data required by the IC Compiler II tool for
placement and routing. The following topics describe how to add the missing technology
data to a reference library:
• Preparing Site Definitions
• Preparing Routing Layers
Note:
In many cases, the LEF file defines the required attributes. You must manually set these
attributes only if you load the physical information by reading a GDSII or OASIS file or if
the LEF file does not define these attributes.

Preparing Site Definitions

The following site attributes are required for placement, but are not defined in the technology
file:
• isDefault site attribute
This attribute identifies the default site for floorplanning. It must be set only on the default
site.
For example, to set the site definition named unit as the default site for floorplanning, use
the following command:
icc2_lm_shell> set_attribute [get_site_defs unit] is_default true

• symmetry site attribute

This attribute defines the site symmetry requirement for cell placement. It must be set on
all sites defined in the technology file. The attribute value is a list that contains one or
more of the following values:
❍ X - the site can be flipped about the x-axis

❍ Y - the site can be flipped about the y-axis

❍ R90 - the site can be rotated 90 degrees

For example, to specify that the site definition named unit can be flipped about the x-axis,
set its symmetry attribute as follows:
icc2_lm_shell> set_attribute [get_site_defs unit] symmetry {X}

To specify that it can be flipped about both the x- and y-axis and can be rotated 90
degrees, use the following command:
icc2_lm_shell> set_attribute [get_site_defs unit] symmetry {X Y R90}

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-13
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

In general, the LEF file defines these site attributes, and the library manager automatically
sets them when you read the LEF file. If you load the physical information by reading a
GDSII or OASIS file or if the LEF file does not define these attributes, use the
set_attribute command to set them manually.

To report the site definitions, use the report_site_defs command.

Note:
The reference library contains only single-height site definitions. The IC Compiler II tool
uses the single-height site definition for both single-height cells and multiple-height cells.

Preparing Routing Layers

The following layer attributes are required for routing, but are not defined in the technology
file:
• routing_direction layer attribute
This attribute identifies the preferred routing direction for the layer. Valid values for this
attribute are horizontal and vertical. For example, to set the preferred routing
direction for the M2 layer as horizontal, use the following command:
icc2_lm_shell> set_attribute [get_layers M2] \
routing_direction horizontal

• track_offset layer attribute

This attribute defines the offset in microns used to create the routing grid for the layer.
The first routing track is located at the specified distance from the placement grid origin.
For example, to set the track offset for the M2 layer as 0.1 micron, use the following
command:
icc2_lm_shell> set_attribute [get_layers M2] track_offset 0.1

In general, the LEF file defines these layer attributes, and the library manager automatically
sets them when you read the LEF file. If you load the physical information by reading a
GDSII or OASIS file or if the LEF file does not define these attributes, use the
set_attribute command to set them manually.

Loading the Logic Libraries

The logic libraries contain the timing, power, and functionality information for the standard
cells and macro cells in the reference library. The supported timing model formats are
generic CMOS, nonlinear delay model (NLDM), and Composite Current Source (CCS).
A reference library should contain this information for all necessary characterization points
(voltages and temperatures for a given process setting). If these characterization points are

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-14
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

represented in multiple logic libraries, you must load all of these logic libraries into a single
library workspace.
Warning:
If multiple reference libraries contain a library cell with the same name, the tool uses the
data from the first reference library in which it finds the cell, and it ignores that cell’s data
in all other reference libraries. This phenomenon is referred to as cell shadowing.
Before loading logic libraries into the library workspace, ensure that they have been
validated with the Library Compiler check_library command. Note that you must have a
Library Compiler license to run this command.
To load logic libraries into the library workspace, use the read_db command.
For example, to load the db1_pvt1.db file, use the following command:
icc2_lm_shell> read_db db1_pvt1.db

To load all the .db files in the current directory, use the following command:
icc2_lm_shell> read_db [glob *.db]

If you specify the files with a relative path or with no path, the tool uses the search path
defined with the search_path variable to locate the files.
When you load a logic library into a library workspace, the library manager performs the
following tasks:
• Creates timing views in the library workspace for each of the blocks in the library source
file
• Saves the logic library attribute settings for the library, library cells, and library cell pins in
the library workspace

If you load more than one logic library into a workspace, the first logic library that you read
is considered the base library. The tool uses the base library for many consistency checks
among the logic libraries loaded for a workspace. If an attribute is defined in more than one
logic library, the tool uses the value from the first logic library in which the attribute is defined.
By default, the tool processes all of the cells defined in the library source file. To process a
subset of the cells, filter the cells as described in Specifying Which Blocks to Process.
By default, the generated reference library contains the timing views generated from all of
the logic libraries loaded into the library workspace. To filter the logic libraries based on your
design operating corners, use the set_pvt_configuration command, as described in
Filtering Logic Libraries Based on Operating Corners.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-15
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

See Also
• Pane
• Defining the Search Path
• Identifying the Process Associated With a Logic Library

Identifying the Process Associated With a Logic Library

When you load a logic library, the library manager uses the following information to identify
the process associated with the pane:
• The process label
The library manager uses the following order of precedence to determine the process
label:
❍ The -process_label option specified with the read_db command
❍ The process_label attribute defined in the operating_conditions group for the
default operating conditions in the logic library
• The process number
The library manager determines the process number from the nom_process attribute for
the library. If this attribute is not specified in the library, the library manager sets the
process number to 1.0.

If two or more libraries have the same process label, process number, voltage values, and
temperature values, the tool uses only the pane generated for the first library, and ignores
the rest. To prevent panes from being ignored, assign a unique process identifier to each
pane. To set the process number or process label after loading a logic library, use the
set_process command.

For example, to read the db1.db logic library and set a process label of PVT1 on the
generated pane, use the following command:
icc2_lm_shell> read_db -process_label PVT1 db1.db

To set a process label of PVT2 on the generated pane after reading the logic library, use the
following command:
icc2_lm_shell> set_process -libraries {db1} -label PVT2

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-16
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Filtering Logic Libraries Based on Operating Corners

By default, the generated reference library contains the timing information from all logic
libraries loaded into the library workspace. To include only the timing information that
matches the valid operating corners (process, voltage, and temperature values) for your
design, define a PVT configuration for the reference library.
A PVT configuration is a sequence of rules, each of which specifies the process labels,
process numbers, voltages, and temperatures to match. If you want all the data that
matches a specific set of operating corners, a single rule is sufficient. If you want to match a
specific subset of many operating corners, you must specify multiple rules.
To define a PVT configuration rule, use the set_pvt_configuration command.
• To create a new rule, use the -add option.
By default, the command uses the rule_n naming convention. To specify the rule name,
use the -name option.
• To modify an existing rule, use the -rule option to specify the rule name.
• To add filters to a rule, use one or more of the following options: -process_labels,
-process_numbers, -voltages, and -temperatures.

• To remove filters from a rule, use the -clear_filter option.

For example, to create a PVT configuration rule that allows any process setting, voltages of
0.65 or 1.32 volts, and a temperature of 25 degrees, use the following command:
icc2_lm_shell> set_pvt_configuration -add \
-voltages {0.65 1.32} -temperatures {25}

Note that this command does not affect loading of the logic libraries. It affects only which
logic libraries are actually used by the reference library. If you change the PVT configuration,
the library manager adjusts the logic library usage appropriately.
To see the logic libraries loaded into the library workspace, use the get_libs command. To
see which logic libraries are actually used by the library workspace based on the PVT
configuration, use the report_workspace command.

Loading Extracted Timing Models

An extracted timing model (ETM) contains the timing information for a design for a single
mode and characterization point. The extracted timing model must be in .db format and must
meet the following additional requirements:
• It must be generated by the PrimeTime tool.
• It must contain a single design.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-17
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• It must not contain a mode definition.

• The dont_touch and dont_use attributes for the design must be set to true.
• The design must have at least one of the following attribute settings:
❍ The timing_model_type attribute has a value of extracted
❍ The interface_timing attribute has a value of true

To load extracted timing models into the library workspace to create timing views, use the
read_db command to load the models in .db format.

You must use the -mode_label option with these commands to specify the mode
associated with the timing arcs and generated clocks defined in the model.
For example, to read the .db file for the model1 extracted timing model, use the following
command:
icc2_lm_shell> read_db -mode_label functional model1.db

If you specify the model files with a relative path or with no path, the tool uses the search
path defined with the search_path variable to locate the files.

Loading the Physical Libraries

The physical libraries contain the geometric shapes for the library cells (standard cells or
macro cells). The library manager uses this information to generate the place-and-route
information (frame views) for the cells.
The physical libraries can be in LEF, GDSII, or OASIS format. In addition, you can load the
physical libraries from a previously saved workspace or reference library, or from the FRAM
views exported from the IC Compiler tool. To learn about loading physical libraries, see the
following topics:
• Reading LEF Files
• Reading GDSII or OASIS Files
• Loading Physical Data from a Reference Library
• Importing Milkyway FRAM Views From the IC Compiler Tool
In some cases, the technology file and physical libraries do not provide all of the information
required by the IC Compiler II implementation tool. For information about the required
information and how to specify it, if it is not loaded automatically, see the following topics:
• Completing the Technology Data
• Completing the Physical Cell Information

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-18
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Reading LEF Files

LEF files contain the shape information for blocks, including the block type, associated site
definition, pins, and connectivity. To read a LEF file into the library workspace, use the
read_lef command. This command supports all versions of LEF through version 5.8. When
the command reads a LEF file, it creates design views for all of the blocks in the file.
For example, to read the myphys.lef file, use the following command:
icc2_lm_shell> read_lef myphys.lef

If you specify the LEF file with a relative path or with no path, the library manager uses the
search path defined with the search_path variable to locate the file.
By default, the read_lef command
• Processes all of the cells defined in the library source file
To process a subset of the cells, filter the cells, as described in Specifying Which Blocks
to Process.
• Creates a design view for each processed block
By default, if a block already has a physical representation in the library workspace, the
tool creates a design view with a new name. To change this default behavior, either use
the -merge_action option to change the behavior for all blocks or use a block mapping
file to specify the behavior for specific blocks. For details, see Handling Duplicate Blocks
in the Physical Libraries.
By default, the read_lef command derives the block boundary from the OVERLAP layer
in the LEF file, if it exists. If it does not exist, the command derives the rectangular block
boundary from the SIZE statement in the LEF file. To derive the rectangular cell
boundary from the SIZE statement even if the OVERLAP layer exists, use the
-cell_boundary by_cell_size option.
If a block has PROPERTY definitions in the LEF file, the read_lef command saves the
properties as user-defined attributes of the block. By default, the command saves all the
block properties; to save only specific block properties, specify the property names with
the -properties option.
When the library manager reads a LEF file, it stores certain settings as attributes on the
blocks or block objects. To use the LEF file only to update the attribute settings on the
existing blocks in the library workspace, and not to create design views, use the
-merge_action attributes_only option.

• Fails if the LEF file contains layer or site information that conflicts with the technology file
For information about resolving site definition conflicts, see Resolving Site Definition
Conflicts When Reading LEF Files.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-19
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

See Also
• Defining the Search Path
• Validating the LEF File
• Determining the Block Types When Reading LEF Files
• Determining the Electrical Equivalence for PG Terminals When Reading LEF Files
• Preparing Standard Cells

Validating the LEF File

To analyze an input LEF file before loading it into the workspace, enable check-only mode
by using the -syntax_only option. The check-only mode provides diagnostic information
about the correctness and integrity of the LEF file. The check-only mode does not load any
information into the workspace.
icc2_lm_shell> read_lef -syntax_only myphys.lef

Determining the Block Types When Reading LEF Files

The read_lef command uses the mapping shown in Table 2-2 to convert the LEF CLASS
properties to design_type attributes for the processed blocks.
Table 2-2 LEF CLASS Property to IC Compiler II design_type Attribute Mapping

LEF syntax IC Compiler II design_type attribute

CLASS property Subtype

BLOCK N/A macro

BLACKBOX black_box
SOFT module

CORE N/A lib_cell

ANTENNACELL diode
FEEDTHRU feedthrough
SPACER filler
TIEHIGH lib_cell
TIELOW lib_cell
WELLTAP well_tap

COVER N/A cover

BUMP flip_chip_pad

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-20
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-2 LEF CLASS Property to IC Compiler II design_type Attribute Mapping (Continued)

LEF syntax IC Compiler II design_type attribute

CLASS property Subtype

ENDCAP BOTTOMLEFT corner

BOTTOMRIGHT corner
POST end_cap
PRE end_cap
TOPLEFT corner
TOPRIGHT corner

PAD N/A pad

AREAIO flip_chip_driver
INOUT pad
INPUT pad
OUTPUT pad
POWER pad
SPACER pad_spacer

RING N/A macro

Determining the Electrical Equivalence for PG Terminals When Reading LEF Files
By default, the read_lef command does not calculate the electrical equivalence (EEQ)
setting for the PG terminals. To calculate the EEQ setting for the PG terminals, use the
-create_eeq_setting_for_block_and_pad option. By default, when the library manager
calculates the EEQ setting, it considers the direction of the PG port. To ignore the port
direction, use the -ignore_pg_direction_for_eeq option.

Resolving Site Definition Conflicts When Reading LEF Files

If the LEF file contains site information that differs from the site information in the technology
file loaded into the library workspace, the read_lef command fails to load the LEF file. Use
one of the following methods to resolve the conflicts so you can load the LEF file:
• If the files contain sites with the same definitions, but different names, you can specify
the site name mapping by using the -convert_sites option with the read_lef
command. For example, to change the site name in the myphys.lef file from unit to
new_unit, use the following command:
icc2_lm_shell> read_lef -convert_sites {unit new_unit} myphys.lef

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-21
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• If the files contain sites with the same names, but different definitions, you can enable the
tool to automatically rename conflicting site names by setting the
file.lef.auto_rename_conflict_sites application option to true before running
the read_lef command.
When you enable this option, the tool uses the following naming convention to rename
the conflicting site names:
lef_file_name.site_name[_n]

The numeric suffix is added only if required to make the site name unique.

Reading GDSII or OASIS Files

GDSII and OASIS files are similar in that they contain physical shape information for the
blocks, but do not contain information about the block type, associated site definition, pins,
or connectivity.
• To read one or more GDSII files into the library workspace and perform connectivity
analysis, use the read_gds command.
• To read one or more OASIS file into the library workspace and perform connectivity
analysis, use the read_oasis command.

If you specify a library source file with a relative path or with no path, the library manager
uses the search path defined with the search_path variable to locate the file.
For example, to read the myphys.gds file, use the following command:
icc2_lm_shell> read_gds myphys.gds

When the tool reads a library source file in GDSII or OASIS format, it assumes that all of the
blocks are standard cells and all of the pins are signal pins. It generates a layout view for
each block in the file. If it finds a duplicate block, it creates a layout view with a new name.
The tool then performs connectivity analysis to determine the pins and connectivity
information and generates a design view for each block.
The following topics describe how to modify the behavior of the read_gds and read_oasis
commands:
• Resolving Layer Differences
• Specifying Which Blocks to Process
• Handling Duplicate Blocks in the Physical Libraries
• Specifying the Site Definitions When Reading GDSII or OASIS Files
• Adjusting Standard Cell Boundaries
• Identifying Power and Ground Pins

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-22
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

• Editing Layout Views Before Performing Connectivity Analysis

• Controlling the Connectivity Analysis of Layout Views

Resolving Layer Differences

When you read a GDSII or OASIS file, the tool assumes that the layer names are the same
in the library source file and the technology file loaded into the library workspace.
• If the layers are the same, but have different names, you must provide a layer mapping
file, as described in Mapping Source File Layers to Technology File Layers.
• If the library source file contains layers that are not defined in the technology file, the tool
creates new layers. For information about other ways to handle this situation, see
Handling Extra Layers in the Library Source File.

Mapping Source File Layers to Technology File Layers

If the layer names differ between the library source file and the technology file, you must
provide a layer mapping file. For information about the syntax of the layer mapping file, see
Layer Mapping File Syntax.
Use one of the following methods to specify the layer mapping file:
• Use the set_layer_map_file -format gds command to load the layer mapping file
into the library workspace
icc2_lm_shell> set_layer_map_file -format gds -map_file file_name

When you load a layer mapping file into the library workspace, it is used by both the
read_gds and read_oasis commands.

• Use the -layer_map option with the read_gds or read_oasis command

icc2_lm_shell> read_gds -layer_map file_name myphys.gds

Handling Extra Layers in the Library Source File

To prevent the tool from creating new layers, use the -read_always false option with the
read_gds or read_oasis command. When you use this option, the command fails if the
library source file contains layers that are not defined in the technology file. To modify this
behavior, use one of the following options with the -read_always false option:
• -mapped_layers_only
In this case, the command loads only those layers specified in the layer mapping file and
ignores all other layers defined in the library source file.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-23
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• -ignore_missing_layers
In this case, the command loads only those layers defined in the technology file and
ignores all other layers defined in the library source file.

You can also set these options in the layer mapping file, as described in Layer Mapping File
Syntax. If you specify these options both on the command line and in the layer mapping file,
the settings in the layer mapping file override the command-line settings.

Specifying the Block Types When Reading GDSII or OASIS Files

GDSII and OASIS files do not specify the block type for the blocks defined in the file. When
you read a GDSII or OASIS file, the tool assumes all blocks are standard cells and sets their
design_type attribute to lib_cell. To specify the block type for the blocks in a GDSII or
OASIS file, create a block mapping file. For information about the syntax of the block
mapping file, see Block Mapping File Syntax. When you run the read_gds or read_oasis
command, use the -block_map option to specify the block mapping file.

Specifying the Site Definitions When Reading GDSII or OASIS Files

GDSII and OASIS files do not specify the site definition associated with the blocks defined
in the file. To enable successful placement and legalization, you must associate each
standard cell with a site definition.
To specify the site definitions for the blocks in a GDSII or OASIS file, create a block mapping
file. For information about the syntax of the block mapping file, see Block Mapping File
Syntax. When you run the read_gds or read_oasis command, use the -block_map option
to specify the block mapping file.
You can also associate site definitions with the standard cells by using the set_attribute
command after loading the library source file, as described in Preparing Standard Cells.

Adjusting Standard Cell Boundaries

When you read a GDSII or OASIS file, the tool determines the boundary for each standard
cell. If a boundary layer is defined, the tool uses it to determine the standard cell boundary.
Otherwise, the tool generates a default boundary.
In some cases, the cell boundary determined by the tool is not correct and you must adjust it.
• If the boundary for a cell is not specified in the library source file and the cell layout
assumes shared power and ground pins, the default boundary generated by the tool is
incorrect. You must adjust the cell boundary by reducing it to the center line of the pin
geometries. Figure 2-3 shows the default and adjusted boundaries for a standard cell
with shared power and ground pins.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-24
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Figure 2-3 Boundary for Standard Cell With Shared Power and Ground Pins

Use one of the following methods to shrink the default boundary:

❍ To automatically shrink the default boundary to the center line of the pin geometries
for all blocks, use the -centerline_boundary option with the read_gds or
read_oasis command.

❍ To shrink the default boundary for specific blocks, specify the

-centerline_boundary option in the block mapping file. For information about the
syntax of the block mapping file, see Block Mapping File Syntax. To specify the block
mapping file, use the -block_map option with the read_gds or read_oasis
command.
• If the boundary for a cell is defined incorrectly in the library source file, manually specify
the boundary by using the set_attribute command to modify the bbox attribute of the
library cell. For example, the script shown in Example 2-1 reduces the boundary for a set
of library cells by 0.115 units on the left side, 0.051 units on the bottom, 0.115 units on
the right side, and 0.109 units on the top.
Example 2-1 Script to Resize Cell Boundaries
set cells_to_resize \
[get_lib_cells -include_subcells {libraryname/*/design } ]
set resize_parameters {-0.115 -0.051 -0.115 -0.051}
foreach_in_collection c $cells_to_resize {
set cname [get_attribute -objects [get_lib_cells $c] -name name]
puts "INFO: Resize boundary for $cname by \{$resize_parameters\}"
set existing_boundary \
[get_attribute -objects [get_lib_cells $c] -name boundary_bbox]
set new_boundary \
[get_attribute -objects \
[get_attribute [resize_polygons \
-objects [create_poly_rect -boundary $existing_boundary] \
-size "$resize_parameters"] \
-name poly_rects] \
-name point_list]
set_attribute [get_lib_cells $c] boundary $new_boundary
}

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-25
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Identifying Power and Ground Pins

GDSII and OASIS files do not specify the pin types. When you read a GDSII or OASIS file,
the tool assumes all pins in the library source file are signal pins.
To identify power and ground pins, use the file.format.port_type_map application
option to map the pin name to its type, where format is either gds or oasis. The mapping
applies to all cells in the GDSII or OASIS files.
For example, to set all pins named VDD as power pins and all pins named VSS as ground
pins when reading GDSII files, use the following command:
icc2_lm_shell> set_app_options -name file.gds.port_type_map \
-value {{power VDD} {ground VSS}}

Editing Layout Views Before Performing Connectivity Analysis

In some cases, you might need to edit the layout views before performing connectivity
analysis. To do this,
1. Read the library source files without performing connectivity analysis by using the
-trace_option none option when you run the read_gds or read_oasis command.

2. Edit the layout views as described in the IC Compiler II Graphical User Interface User
Guide.
3. Perform connectivity analysis by running the trace_connectivity command.

Controlling the Connectivity Analysis of Layout Views

The tool uses the text labels in the library source file to associate metal shapes with a net or
pin. If the text is not on the same layer as the metal shape, you must map the text layers to
the metal layers, as described in Mapping Text Layers.
The tool traces the connectivity of the labeled metal shapes to identify additional metal
shapes associated with that net or pin. It can trace connectivity for shapes that overlap pin
text, for shapes on the same layer as the pin text, or for shapes on all layers. By default, the
tool determines the pin tracing method based on the block type. To explicitly specify the pin
tracing method, use the -trace_option option with the read_gds or read_oasis
command or the -layer option with the trace_connectivity command. Table 2-3
describes the supported methods, the keywords used to enable them, and the default
method for each block type.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-26
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-3 Pin Tracing Methods

Tracing method Cell types for which this is the -trace_option -layer
default tracing method Keyword Keyword

Create terminal shapes only 1

Modules, macro cells , analog pins_only pins_only
for shapes that overlap pin cells, and black box cells
text.

Trace the connectivity only on Library cells, pad cells, corner same_layer same
the same layer as the pin text.2 cells, pad spacer cells, cover
cells, flip-chip pads, flip-chip
drivers, physical-only cells, well
tap cells, end cap cells, diode
cells, filler cells, and metal fill

Trace the connectivity across N/A all_layers all

all layers.2

1. If a macro cell has rectilinear pins, you must explicitly set the -trace_option option to same_layer; the
pins-only method always extracts rectangular pins.
2. To reduce runtime, limit the number of geometries traced by setting the -trace_connectivity_limit option
or enable all-layer tracing only for specific pins by using the -trace_all_layers_for option.

Mapping Text Layers

If the text is not on the same layer as the metal shape, you must use the
file.format.text_layer_map application option to map the text layers to the metal
layers, where format is either gds or oasis. Use the following format to specify the mapping:
{metal_layer {text_layer1[:data_type1] [text_layer2[:data_type2] ...]}}

where
• metal_layer and text_layer are the layer names in the technology file
• data_type, which is optional, is the data type number in the technology file

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-27
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Layer Mapping File Syntax

The syntax used to specify the layer mapping in the layer mapping file is
[object_type] tf_layer[:tf_purpose][:use_type][:mask_type]
stream_layer[:stream_data_type]

where
• object_type specifies the types of objects to which the mapping applies
Valid values are data (all non-text objects), text, and all. The default is all.
• tf_layer is the layer number in the technology file, which is a required argument
• tf_purpose is the purpose number in the technology file
Valid values are either an integer value or the drawing keyword.
• use_type is the usage of the geometries in the design
Valid values are power, ground, signal, clock, boundary,
hard_placement_blockage, soft_placement_blockage, routing_blockage, and
area_fill.

• mask_type is the mask constraint of the geometries

Valid values for metal layers are mask_one, mask_two, mask_three, and mask_same. Via
layers have the following additional valid values: MASK_FOUR, MASK_FIVE, MASK_SIX,
MASK_SEVEN, MASK_EIGHT, MASK_NINE, MASK_TEN, MASK_ELEVEN, MASK_TWELVE,
MASK_THIRTEEN, MASK_FOURTEEN, and MASK_FIFTEEN.

• stream_layer is the layer number in the GDSII or OASIS file, which is a required
argument
• stream_data_type is the data type in the GDSII or OASIS file

To include comment lines in the layer mapping file, start the line with a semicolon (;).
The layer mapping file also supports the following optional statements to further control how
the read_gds or read_oasis command loads the library source files:
read_always true|false [-mapped_only] [-ignore_missing_layers]
blockage_as_zero_spacing true|false
cell_prop_attribute attribute_value
net_prop_attribute attribute_value
pin_prop_attribute attribute_value

Table 2-4 describes how these statements affect the behavior of the read_gds and
read_oasis commands. You can also specify most of these settings on the command line.
If you set an option both on the command line and in the layer mapping file, the setting in the
layer mapping file takes precedence.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-28
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-4 Additional Layer Mapping File Statements

Mapping file statement Command-line option Description

read_always true -read_always true The command loads all layers defined
in the library source file. If the library
source file contains layers that are not
defined in the technology file, the
command creates new layers.
This is the default behavior.

read_always false -read_always false The command issues an error

message and fails if the library source
file contains layers that are not
defined in the technology file.

read_always false -read_always false The command loads only those layers
-mapped_only -mapped_layers_only specified in the layer mapping file and
ignores all other layers defined in the
library source file.

read_always false -read_always false The command loads only those layers
-ignore_missing_layers -ignore_missing_layers defined in the technology file and
ignores all other layers defined in the
library source file.

blockage_as_zero_spacing N/A The command does not mark

false blockages read from the library
source file as zero-spacing
blockages.
This is the default behavior.

blockage_as_zero_spacing N/A The command marks blockages read

true from the library source file as
zero-spacing blockages.

cell_prop_attribute -cell_property The command sets the cell instance

attribute_value attribute_value names by using the name associated
with the specified attribute value.

net_prop_attribute -net_property The command associates geometries

attribute_value attribute_value with nets by using the specified
attribute value.

pin_prop_attribute -pin_property The command associates geometries

attribute_value attribute_value with pins by using the specified
attribute value.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-29
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

The following example shows a layer mapping file. The comments describe how the
statements affect the behavior of the read_gds and read_oasis commands.
Example 2-2 Layer Mapping File
; Disable new layer creation
read_always false

; Map GDSII or OASIS layer 10 with data type 2 to power net shapes
; on technology file layer 56 with a purpose of 4
data 56:4:power 10:2

; Map GDSII or OASIS layers 31 and 32 with data type 0 to

; technology file layer 31 with a purpose of 0
data 31:0 31:0
data 31:0 32:0

Loading Physical Data from a Reference Library

To load the physical data from a complete or frame-only reference library into the current
library workspace, use the read_ndm command. If the reference library contains technology
data, the command also loads this information. By default, the library manager loads all
existing physical views (design, frame, and layout) of the cells into the library workspace. To
load only specific views, use the -views option.
Note:
For the aggregate flow, the library manager ignores the -views option and always loads
all available views, including the timing views.
For example, to load the physical data from the myphys.ndm frame-only library into the
current library workspace, use the following command:
icc2_lm_shell> read_ndm myphys.ndm

When you load frame views from a reference library, the library manager verifies that the
frame views in the reference library are consistent with any existing frame views in the
library workspace and issues a warning message if it finds inconsistencies.
Each time you run the command, you can specify only a single library file to load; to load
multiple libraries, you must run the command multiple times. In addition, this command
loads only reference libraries; you cannot use this command to load aggregate libraries.
You can specify the library file with an absolute path, a relative path, or no path. If you
specify the file with a relative path or with no path, the library manager uses the search path
to find the file.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-30
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Loading Physical Data from a Design Library

If you are using the ETM flow, you load the physical data for the extracted timing models
from the design library. To load the design library into the current library workspace, use the
read_ndm command.
Note:
You can load design libraries only when using the ETM flow; if you are using another
flow, the tool issues an error.
By default, the library manager loads all existing physical views (design, frame, and layout)
of the blocks with an empty label into the library workspace.
• To load only specific views, use the -views option.
• To load the blocks with a specific label, use the -label option.

For example, to load the physical data for blocks with the empty label from the myblock.ndm
design library into the current library workspace, use the following command:
icc2_lm_shell> read_ndm myblock.ndm

To load the physical data for blocks with a label of mylabel from the myblock.ndm design
library into the current library workspace, use the following command:
icc2_lm_shell> read_ndm -label mylabel myblock.ndm

Note:
The generated library does not contain labels, regardless of the options used with the
read_ndm command.

When you load frame views from a design library, the library manager verifies that the frame
views in the design library are consistent with any existing frame views in the library
workspace and issues a warning message if it finds inconsistencies.
Each time you run the command, you can specify only a single library file to load; to load
multiple libraries, you must run the command multiple times.
You can specify the library file with an absolute path, a relative path, or no path. If you
specify the file with a relative path or with no path, the library manager uses the search path
to find the file.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-31
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Importing Milkyway FRAM Views From the IC Compiler Tool

If you do not have source files for your physical libraries, but do have Milkyway FRAM views
in an IC Compiler reference library, you can use these to create an IC Compiler II frame-only
reference library. You can then use this frame-only reference library to create a complete
IC Compiler II reference library.
To create a frame-only reference library by importing Milkyway FRAM views from the
IC Compiler tool,
1. In the IC Compiler tool, export the Milkyway FRAM views of a reference library by using
the export_icc2_frame command.
For example, to export all FRAM views of all reference libraries of the my_lib design
library, use the following commands:
icc_shell> open_mw_lib my_lib
icc_shell> export_icc2_frame

The IC Compiler tool writes out a set of files into a new directory named icc2_frame. The
generated files include the technology files and a tar file that contains the FRAM views
converted to LEF format.
2. In the IC Compiler II Library Manager tool, create a frame-only library workspace by
using the create_workspace -flow frame command.
For example, to create a library workspace using the technology data exported from the
IC Compiler tool for the my_reflib reference library, use the following command:
icc2_lm_shell> create_workspace -flow frame \
-technology /path/icc2_frame/data/TF/my_reflib.tf my_workspace

3. Import the converted FRAM views generated by the IC Compiler tool into the library
workspace by using the import_icc_fram command.
For example, to import the converted FRAM views exported from the IC Compiler tool for
the my_reflib reference library, use the following command:
icc2_lm_shell> import_icc_fram \
/path/icc2_frame/data/LEF/my_reflib.tar.gz

Note:
You cannot mix imported Milkyway FRAM data with other physical data, such as LEF,
GDSII, or OASIS data. If you use imported Milkyway FRAM data, all physical data in
the library workspace must come from imported Milkyway FRAM data.
4. Validate the workspace, as described in Validating the Workspace.
5. Commit the workspace, as described in Committing the Workspace.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-32
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

See Also
• Building Reference Libraries
• Loading Physical Data from a Reference Library

Specifying Which Blocks to Process

By default, when you load logic libraries or physical libraries, the tool processes all of the
cells defined in the library source file. If you need to process only a subset of the cells, you
can
• Exclude cells from processing
❍ Use the lib.workspace.exclude_design_filters application option to specify
the excluded blocks.
or
❍ Load all of the blocks into the library workspace and then remove the unwanted
blocks by using the remove_lib_cell command.
• Read only specific blocks when loading the source files
Use the lib.workspace.include_design_filters application option to specify the
blocks to read when loading the source files.

Handling Duplicate Blocks in the Physical Libraries

To avoid adding duplicate blocks when reading LEF, GDSII, and OASIS files, use the
following options to specify how to handle these blocks. You can
• Ignore the duplicate block by using the -merge_action ignore option
• Replace the existing block with the new block by using the -merge_action overwrite
option
• Merge the geometries of the new block with the existing block by using the
-merge_action update option

• Add the block with a new name by using the -merge_action add option, which is the
default
• Specify the handling for specific blocks in a block mapping file by using the -block_map
file_name option
The settings in the block mapping file override the -merge_action setting. For
information about the block mapping file syntax, see Block Mapping File Syntax.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-33
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Block Mapping File Syntax

The syntax used to specify the block mapping in the block mapping file is
block_name[:rw_type[, flatten][:levels]] [block_type][-fixed_mask]
[-site_name site_name] [-centerline_boundary]

Note:
The read_lef command supports only the block_name and rw_type arguments; it
ignores all other arguments.
The arguments are defined as follows:
• block_name is the name of the block, which is required
You can use regular expressions to specify the block names; the read_lef, read_gds,
and read_oasis commands use glob-style pattern matching to identify the blocks.
When you use a block mapping file with the read_gds or read_oasis command, any
blocks that do not match a pattern in the block mapping file are loaded into the library
workspace as standard cells.
• rw_type specifies how to load the block into the library workspace
This argument overrides the default behavior specified by the -trace_option option of
the read_gds or read_oasis command for the specified blocks. Valid values for this
argument are
❍ add
Creates a physical representation for the block; if a physical representation already
exists for the block, it creates a physical representation with a new name.
❍ ignore
Does not create a physical representation for the block. The read_gds and
read_oasis commands ignore this setting if the block is a subblock of a hierarchical
block.
❍ overwrite
Creates a new physical representation that replaces the existing physical
representation for the block.
❍ update
Updates the existing physical representation for the block by merging the new data
with the existing data.
❍ retain
Keeps the instance but does not create the reference library cell.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-34
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

❍ flatten (supported only by the read_gds and read_oasis commands)

Flattens all the instances of the block.
You can specify flatten either as the rw_type argument or as a modifier for the
rw_type argument. If you specify flatten as the rw_type argument, the tool treats
this the same as if you specified add, flatten.
When you specify this keyword, by default, the read_gds and read_oasis
commands perform one level of flattening. To flatten more than one level of hierarchy,
specify the levels argument.
• levels specifies the number of levels to flatten
This argument is valid only when flattening is enabled.
• block_type is the block type; valid values are lib_cell, macro, pad, corner,
pad_spacer, cover, flip_chip_pad, flip_chip_driver, analog, black_box,
feedthrough, well_tap, abstract, end_cap, diode, filler, and fill
If you do not specify this argument, the read_gds and read_oasis commands use a
type of lib_cell.
• -fixed_mask sets the is_mask_shiftable attribute for the block to false
This argument overrides the -mask_fixed option of the read_gds or read_oasis
command for the specified blocks.
• -site_name sets the site_name attribute for the block to the specified value
Each standard cell in a library source file must be associated with a site definition. Use
this option to override the default site definition for a specific cell. You can also specify
the site definition for a library cell by using the set_attribute command to set its
site_name attribute.
For more information about setting the site definitions, see Preparing Standard Cells.
• -centerline_boundary shrinks the default boundary to the center line of the pin
geometries for the block
This argument overrides the -centerline_boundary option of the read_gds or
read_oasis command for the specified blocks.
For more information about adjusting the block boundary, see Adjusting Standard Cell
Boundaries.

To include comment lines in the block mapping file, start the line with a semicolon (;).

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-35
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

The following example shows a block mapping file. The comments describe how the
statements affect the behavior of the read_gds and read_oasis commands.
Example 2-3 Block Mapping File
; Load all blocks with CORE in their name as macro cells
*CORE*:add macro

; Flatten all blocks with filler in their name

*filler*:flatten

; Flatten all blocks with MEM in their name two levels deep
*MEM*:flatten:2

; Ignore the rest of the blocks, they will be loaded only when they
; happen to be in a *CORE* block’s hierarchy
*:ignore

Creating Scaling Groups

A scaling group enables the IC Compiler II tool to perform timing analysis and optimization
at intermediate voltage and temperature operating conditions. You can create a scaling
group when the voltage and temperature combinations of the logic libraries for a given
process form a complete grid.
When deciding whether to create scaling groups, you need to consider the effect of the
index values (breakpoints) used for the timing arc lookup tables in each library.
• If the breakpoints for all the lookup table indexes for a given arc are the same for all the
characterization points, you should create scaling groups because you gain efficiency in
delay calculation with a minimal impact on memory usage.
• If the breakpoints for at least one index in the lookup table are the same for all the
characterization points, you can create scaling groups, but there is a larger impact on
memory usage.
• If the breakpoints for all indexes in the lookup table for a given arc differ among the
characterization points, you cannot create scaling groups because the memory cost is
too high.

To create a scaling group, use the create_scaling_group command to specify the logic
libraries in the scaling group. The create_scaling_group command verifies that the
specified libraries meet the requirements; if they do not meet the requirements, the
command fails and issues an error message. When you run the check_workspace
command, the tool performs further validation of the scaling groups (for details, see Scaling
Group Checks).
For example, assume that you load four logic libraries with a process label of TYP: one at
1.0V and 0°C (typ_pvt1.db), one at 1.0V and 125°C (typ_pvt2.db), one at 0.8V and 0°C

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-36
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

(typ_pvt3.db), and one at 0.8V and 125°C (typ_pvt4.db). To create a scaling group using
these logic libraries, use the following command:
icc2_lm_shell> create_scaling_group \
[get_libs {typ_pvt1 typ_pvt2 typ_pvt3 typ_pvt4}]

In the reference library, the scaling group is represented as a single pane that covers the
whole range of voltages and temperatures.
You can define any number of scaling groups, but a logic library can appear in only one
scaling group. A reference library can contain some logic libraries in scaling groups, and
others standalone.

See Also
• Scaling Group
• Breakpoints
• Loading the Logic Libraries

Loading Parasitic Parameters

The TLUPlus files contain the RC coefficients for a specific technology. The TLUPlus
models enable accurate RC extraction results by including the effects of width, space,
density, and temperature on the resistance and capacitance coefficients.
To read a TLUPlus file into the library workspace, use the read_parasitic_tech
command. You must specify the TLUPlus files by using the -tlup option. If you specify the
TLUPlus files with a relative path or with no path, the library manager uses the search path
defined with the search_path variable to locate the files.
If the layer names in the TLUPlus file do not match the layer names in the technology file,
you must use the -layermap option to specify the layer mapping file. The layer mapping file
uses the following format:
conducting_layers
tf_metal_layer_name1 ITF_metal_layer_name1
...
tf_metal_layer_namen ITF_metal_layer_namen

via_layers
tf_via_layer_name1 ITF_via_layer_name1
...
tf_via_layer_namen ITF_via_layer_namen

To include comments in the layer mapping file, start the line with an asterisk (*) or pound
sign (#).

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-37
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

After you read in a TLUPlus file, it is identified by its parasitic technology model name. By
default, the parasitic technology model name is the base name of the specified TLUPlus file;
however, you can specify a different name by using the -name option.
For example, to read in a TLUPlus file named my.tlup using a layer mapping file named
my.layermap and store it in the workspace with a parasitic technology model name of para1,
use the following command:
icc2_lm_shell> read_parasitic_tech -tlup my.tlup \
-layermap my.layermap -name para1

Loading Signal Electromigration Constraints

The signal electromigration constraints are defined in either an Interconnect Technology
Format (ITF) file or an Advanced Library Format (ALF) file. To load these constraints into the
library workspace, use the read_signal_em_constraints command.
• By default, the command assumes that the file is in ITF format.
For example, to load the electromigration constraints from an ITF file named em.itf, use
the following command:
icc2_lm_shell> read_signal_em_constraints em.itf

• To read an ALF file, use the -format ALF option.

To load the electromigration constraints from an ALF file named em.alf, use the following
command:
icc2_lm_shell> read_signal_em_constraints -format ALF em.alf

If the library workspace already contains signal electromigration constraints, it is replaced by

the data in the new file.

Completing the Physical Cell Information

The physical libraries might not contain all of the information required by the IC Compiler II
tool for placement and routing. The following topics describe how to annotate missing
physical information for a reference library:
• Preparing I/O Cells
• Preparing Standard Cells
• Preparing Macros

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-38
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Preparing I/O Cells

I/O cells must have the following attributes to identify their physical characteristics:
• design_type library cell attribute
This attribute specifies the I/O cell type. I/O cells must have one of the following settings
for the design_type attribute: corner, pad, pad_spacer, flip_chip_driver, or
flip_chip_pad.

• reference_orientation library cell attribute

This attribute specifies the orientation for proper placement of the I/O cell in the bottom
I/O guide. Modify this attribute to correct any I/O orientation issues.
• class terminal attribute
This attribute specifies the I/O pin type and is required for the flip-chip flow. Valid values
for the class attribute are bump, core, and none.

In general, the LEF file defines these attributes, and the library manager automatically sets
them when you read the LEF file. If you load the I/O cells by reading a GDSII or OASIS file
or if the LEF file does not define these attributes, use the set_attribute command to set
them manually.

Preparing Standard Cells

Standard cells must have the following attributes to enable placement and legalization in the
IC Compiler II tool:
• site_name library cell attribute
This attribute identifies the site definition associated with the standard cell. If a standard
cell does not have a site definition or its site definition does not match a site definition in
the technology file, the IC Compiler II tool cannot place the cell.
Note:
Use the single-height site definition, which is often named unit, for both single-height
and multiple-height cells. The IC Compiler II tool automatically identifies the polarity
of the power and ground pins and places the single-height and the multiple-height
cells accordingly.
For example, to associate the site definition named unit with all cells in the workspace,
use the following command:
icc2_lm_shell> set_attribute -objects [get_lib_cells */*/design] \
-name site_name -value unit

To report the site definitions in the technology file, use the report_site_defs
command.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-39
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• boundary library cell attribute

This attribute defines the boundary of the standard cell. The height of a standard cell
must be the same as the height of its site definition and the width must be an integer
multiple of the width of its site definition.
For information about changing the boundary attribute, see Adjusting Standard Cell
Boundaries.

In general, the LEF file defines these attributes, and the library manager automatically sets
them when you read the LEF file. If you load the standard cells by reading a GDSII or OASIS
file or if the LEF file does not define these attributes, use the set_attribute command to
set them manually.

See Also
• Resolving Site Definition Conflicts When Reading LEF Files
• Specifying the Site Definitions When Reading GDSII or OASIS Files
• Defining Antenna Properties on Standard Cells

Preparing Macros
To enable antenna checking on hard macro cells, use one of the following methods to
annotate hierarchical antenna properties on their ports:
• Automatically extract the antenna properties by enabling IC Validator antenna extraction
during the check_workspace command, as described in Automatic Antenna Property
Extraction Using the IC Validator Tool.
• Manually annotate the antenna properties on the hard macro ports by using the
set_port_antenna_property command, as described in Defining Antenna Properties
on Hard Macro Cells.

Automatic Antenna Property Extraction Using the IC Validator Tool

To enable IC Validator antenna extraction during the check_workspace command, perform
the following tasks before running the check_workspace command:
• Specify the location of the IC Validator executable by setting the ICV_HOME_DIR
environment variable.
You can set this variable in your .cshrc file. To specify the location of the IC Validator
executable, use commands similar to those shown in the following example:
% setenv ICV_HOME_DIR /root_dir/icv
% set path = ($path $ICV_HOME_DIR/bin/AMD.64)

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-40
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Make sure that the version of the IC Validator executable that you specify is compatible
with the IC Compiler II version that you are using.
For more information about the IC Validator tool, see the IC Validator documentation,
which is available on SolvNet.
• Set the signoff.antenna.enabled application option to true.
• Set signoff.antenna application options to control the extraction behavior.
For a summary of these options, see Antenna Extraction Application Options.

Querying the Workspace

To see the contents of a library workspace, use the report_workspace command. By
default, the command reports the following information:
• The workspace name
• The technology file loaded into the workspace
• The logic libraries loaded into the workspace
You can optionally report the PVT and power rail information for each logic library by
using the -panes option.
• The physical libraries loaded into the workspace
• The TLUPlus files loaded into the workspace
• The validation status of the workspace

For example,
icc2_lm_shell> report_workspace

Workspace name: myreflib

...Checked? No

...Technology file: /usr/LIBRARIES/TECH/my.tf

...DB/Liberty files:
1. /usr/LIBRARIES/DB/my_ff0p95v125c.db
2. /usr/LIBRARIES/DB/my_ff0p95vn40c.db
3. /usr/LIBRARIES/DB/my_ff1p16v125c.db
4. /usr/LIBRARIES/DB/my_ff1p16vn40c.db

...Physical Source files:

1. /usr/LIBRARIES/LEF/my.lef

...TLUP files: /usr/LIBRARIES/TLU/my.tlup

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-41
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Validating the Workspace

To validate the contents of the library workspace, use the check_workspace command.
icc2_lm_shell> check_workspace

In addition to validating the workspace, the check_workspace command performs the

following tasks:
• Generates the frame views of the physical cells in the workspace
For information about generating frame views, see Generating Frame Views.
• Sets the is_secondary_pg attribute for PG pins
For information about the secondary PG settings, see Identifying Secondary PG Pins.
• (Optional) Extracts the antenna properties
For information about extracting antenna properties, see Automatic Antenna Property
Extraction Using the IC Validator Tool.
When you run the check_workspace command, the tool performs the checks described in
the following topics:
• Library Checks (includes checks for unique characterization points)
• Cell Checks (includes checks for missing cells, differences in logic function, and
differences in the cell attributes)
• Pin Checks (includes checks for missing pins, and differences in the pin direction, type,
and order)
• PG Rail Checks (includes checks for differences in the number, names, and order)
• Timing Arc Checks (includes checks for missing arcs, incorrect arcs, and differences in
breakpoints)
• Scaling Group Checks (includes checks for unique libraries for each characterization
point, and differences in threshold value settings and timing arc breakpoints)
• Leakage-Power Checks (includes checks for missing leakage-power information and
differences in power conditions)

In many cases, the library manager can automatically fix the issues detected by these
checks.
Note:
The checks performed by the check_workspace command validate the consistency of
the library source files loaded into the workspace; however, the workspace might not

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-42
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

contain all of the information required by the IC Compiler II tool for placement and
routing. For information about completing the information, see the following topics:
❍ Completing the Technology Data
❍ Completing the Physical Cell Information
To generate a reference library from a library workspace, the workspace must pass these
checks. However, in some cases you can generate a reference library using incomplete or
inconsistent source libraries by defining a mismatch configuration, as described in Allowing
Incomplete or Inconsistent Library Data. Reference libraries created with a nondefault
mismatch configuration are not valid for implementation and can be used only for preroute
feasibility analysis; these types of libraries are referred to as prototype libraries.
You can view the messages issued by the check_workspace command in the message
browser, as described in Using the Message Browser Window.
To generate more detailed messages during the validation, use the -details option with
the check_workspace command to specify one or more of the following categories:
arcs_progress, breakpoint_comparisons, combine_physical, leakage_progress,
physical_only_cells, scaling_group_info, or all.
Note:
Using the -details option can result in a very large log file. In general, you should run
the check_workspace command with the -details option only to debug a specific
issue.

Library Checks
The check_workspace command performs the following library checks:
• The library workspace contains at least one physical library.
• Each library logic loaded into the workspace has a unique characterization point
(process, voltage, and temperature).

The workspace must pass these checks before it can be committed.

PG Rail Checks
This topic describes the PG rail checks for logic libraries that use the PG-pin syntax. For
information about PG rail checks for older logic libraries that do not use the PG-pin syntax,
see Using Non-PG Logic Libraries.
Note:
You cannot mix logic libraries with and without PG-pin syntax in a library workspace.
Logic libraries that use the PG-pin syntax define the PG pin connections by using
library-level voltage_map attributes and cell-level pg_pin groups. The voltage_map

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-43
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

attributes define the power rail names. The pg_pin groups define the PG pin connections
for a cell; they use the voltage_name attribute to assign one of the defined power rails to
each PG pin. The signal pins of a cell are associated with the PG rails by using the pin-level
related_power_pin and related_ground_pin attributes. Example 2-4 shows the use of
these attributes to define the power connections in a .lib logic library file.
Example 2-4 Logic Library Example With voltage_map Attributes
library (my_lib) {
...
voltage_map(VDD085, 0.85);
voltage_map(VDD105, 1.05);
voltage_map(VDD120, 1.20);
...
cell(LS_085_105) {
pg_pin (VDDH) {
voltage_name : VDD105;
pg_type : primary_power;
}
pg_pin (VDDL) {
voltage_name : VDD085;
pg_type : primary_power;
}
...
pin (in) {
direction : input;
related_power_pin : VDDL;
related_ground_pin : VSS;
...
}
pin (out) {
direction : output;
related_power_pin : VDDH;
related_ground_pin : VSS;
...
}
...
} /* end cell group*/
...
} /* end library group*/

The check_workspace command verifies that each logic library has the same number of
rails and that the rails have the same names and types. However, the tool ignores rails that
are defined in a voltage_map attribute but not used.
If the rail order differs, the tool automatically updates the order using the information from
the base library.
By default, if a rail name differs between the logic libraries, the tool issues an LM-043 error.
If the mismatch is caused only by rail names and positions, and not rail type differences, you
can use the rename_rail command to make the rail names match. For example, assume
logic library A has a voltage_map setting of (VDD1.0, 1.0) and logic library B has a

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-44
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

voltage_map setting of (VDD1.1, 1.1). You could use the rename_rail command to align
these rails, as shown in the following example:
icc2_lm_shell> rename_rail -library A -from VDD1.0 -to VDD
icc2_lm_shell> rename_rail -library B -from VDD1.1 -to VDD

In some cases, it might be difficult to find a combination of rename_rail commands that

result in a consistent set of rail names. In these situations, you can have the tool assign the
rail names instead of using the rail names from the logic libraries.
To enable the tool to assign the rail names, set the lib.logic_model.use_db_rail_names
application option to false. In that case, the tool analyzes the voltage values for all of the
power and ground pins on the library cells in all logic libraries and assigns a rail name to
each unique combination. The generated rail names use the format type_n, where type is
the rail type, such as power or ground, and n is an integer that is incremented to make each
name unique. You can use the rename_rail command to change the generated rail names
to names that are more meaningful to you.
Note:
If the logic libraries contain duplicate rails, the number of rails generated by the tool will
be less than the number of rails in the logic libraries. Because of this difference, the
check_workspace command issues errors; you can ignore these errors, as they are
followed by a message stating that rail mismatches have been fixed.

Cell Checks
To learn about the cell checks performed by the check_workspace commands, see the
following topics:
• Missing Cell Checks
• Logic Function Check
• Cell Attribute Checks

Missing Cell Checks

The check_workspace command checks for the following types of missing cells:
• A cell that exists in some, but not all logic libraries, and you are using the normal flow
The tool issues an error message if it finds missing or extra cells in a logic library, as
compared to the set of cells in the base library.
Note:
The cell name checks are case-sensitive. You can create a prototype library using
case-insensitive checks by defining a mismatch configuration, as described in
Allowing Incomplete or Inconsistent Library Data.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-45
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

To create a reference library, you must do one of the following:

❍ Manually fix the source libraries and then rerun the check_workspace command
❍ Rerun the check_workspace command with the -allow_missing option to enable
the tool to add the missing cells to the generated reference library
The generated reference library will contain all cells that exist in at least one logic
library; if a cell does not exist in a logic library, it will have missing data in the pane
associated with that logic library.
• A cell that exists in the logic libraries, but not in any physical library
If a cell exists in the logic libraries, but not in any physical library, the tool issues an error
message and you cannot commit the workspace.
To create a reference library, you must either
❍ Set the lib.logic_model.auto_remove_timing_only_designs application option
to true to automatically remove the cells from the workspace
❍ Manually remove the cells from the workspace by using the remove_lib_cell
command
❍ Update the source libraries
To create a prototype library that includes placeholder cells for the missing physical cells,
define a mismatch configuration, as described in Allowing Incomplete or Inconsistent
Library Data.
• A cell that exists in a physical library, but not in the logic libraries
If a cell exists in a physical library, but not in any logic library, the tool behavior depends
on the flow you selected.
❍ For the normal flow, the cell is not included in the generated reference library.
❍ For the physical-only flow, the cell is included in the generated reference library.
For detailed information about physical-only cells detected during workspace validation,
specify the physical_only_cells keyword with the -details option.

Logic Function Check

The check_workspace command verifies that the logic function for a cell is equivalent in all
of the logic libraries.
Cells with the same name in different logic libraries must have an equivalent logic function
and the pin_equal and pin_opposite relationships must match; otherwise, the tool issues
an error message. You must manually correct this error before you can continue with library
preparation. You can correct this error either by updating the library source file and reloading
it, or by using the remove_lib_cell command to remove the cell.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-46
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Cell Attribute Checks

The check_workspace command checks the dont_touch, dont_use, and
use_for_size_only attributes for each cell in the logic libraries.

By default, if a cell with the same name in different logic libraries has different values for any
of these attributes, the tool issues a warning message and stores the attribute value from the
base library in the reference library. You can resolve conflicts by using the set_attribute
command to change the attribute values.
To require a cell to have the same value for these attributes in all logic libraries, set the
lib.logic_model.require_same_opt_attrs application option to true.

Pin Checks
To learn about the pin checks performed by the check_workspace commands, see the
following topics:
• Missing Pin Checks
• Pin Definition Checks

Missing Pin Checks

The check_workspace command compares the pins defined for a cell in each logic and
physical library against the pins defined for the cell in the base library. If a cell in any library
(logic or physical) in the workspace is missing one or more pins as compared to the base
library, the tool issues an error message.
Note:
The pin name checks are case-sensitive. You can create a prototype library using
case-insensitive checks by defining a mismatch configuration, as described in Allowing
Incomplete or Inconsistent Library Data.
The tool automatically fixes the following issues:
• If a cell in the physical library has power or ground pins that are not defined in the logic
libraries, the tool automatically adds these pins to the logic cell.
• If a pin is defined as a signal pin in the logic library, but is defined as a PG pin in the
physical library, the tool issues a warning, redefines the pin as a PG pin, and removes all
timing information from the pin.

To create a reference library, you must manually fix any other types of errors in the source
libraries. If the pins are not actually missing, but the pin names differ between libraries, you
can fix this issue by using the set_attribute command to update the name attribute for the
pins.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-47
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

To create a prototype library that includes placeholder pins for the missing pins, define a
mismatch configuration, as described in Allowing Incomplete or Inconsistent Library Data.

Pin Definition Checks

The check_workspace command checks the following aspects of the pin definition:
• Pin direction
If a pin in any library (logic or physical) in the workspace has a different direction as
compared to the base library, the tool issues an error message, with the following
exceptions:
❍ The pin is defined as a bidirectional power or ground (PG) pin in the physical library
and is defined as an input or output PG pin in the base library. In this case, the tool
uses the direction defined in the base library.
❍ The pin does not have a direction in the physical library, as is the case when you read
GDSII or OASIS files. In this case, the tool uses the pin direction from the logic
libraries.
To create a reference library, you must manually fix the source libraries.
To create a prototype library that uses the pin direction from the base library in the case
of mismatches, define a mismatch configuration, as described in Allowing Incomplete or
Inconsistent Library Data.
• Pin type
The tool automatically fixes the following issues:
❍ If a pin does not have a pin type in the physical library, as is the case when you read
GDSII or OASIS files, the tool uses the pin type from the logic libraries.
❍ If a pin is defined as a signal pin in the logic library, but is defined as a PG pin in the
physical library, the tool issues a warning, redefines the pin as a PG pin, and removes
all timing information from the pin.
To generate a reference library, you must manually fix the following issues:
❍ A pin is defined as a signal pin in all logic libraries, but the bit_width, is_pad,
is_diode, or is_scan attribute setting differs
To fix this issue, you can use the set_attribute command to change the attribute
values.
❍ A pin is defined as a signal pin in one logic library, but is defined as a PG pin in
another logic library
If a pin is incorrectly defined as a signal pin and is not used in the logic function
definition, you can fix this issue by using the set_attribute command to change the
port_type attribute of the pin.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-48
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Note:
Changing a pin from a signal pin to a PG pin might cause the tool to remove timing
arcs for that pin.
You can use the set_attribute command only to change a signal pin to a PG
pin; you cannot change a PG pin to a signal pin.
❍ A pin is defined as a PG pin in all logic libraries, but the pg_type attribute differs
To fix this issue, you can use the set_attribute command to change the pg_type
attribute of the pin.
To create a prototype library that uses the pin type from the base library in the case of
mismatches, define a mismatch configuration, as described in Allowing Incomplete or
Inconsistent Library Data.
Note:
The mismatch configuration can only change a signal pin to a PG pin; it cannot
change a PG pin to a signal pin.
• PG pin connection
If the rail name specified for the voltage_name attribute in a pg_pin group is not defined
in a library-level voltage_map attribute or the voltage_name attribute for a PG pin differs
between libraries, the tool issues an error message. To fix this error, you can use the
set_attribute command to change the rail_name attribute. To see the rail names
defined for a library workspace, use the report_workspace -panes command.
• Related PG pin
Signal pins have a related power pin and a related ground pin; power pins can have a
related bias pin. Typically, these relationships are defined in the logic libraries.
If the logic libraries do not define these relationships, either because they do not define
the PG pins (and the PG pins are inherited from the physical library) or they define the
PG pins, but not the relationships, the check_workspace command tries to derive these
relationships as follows:
❍ If a cell has a single power pin and a single ground pin, the tool automatically derives
the related PG pin information.
❍ If a cell has multiple power pins, you must guide the tool to derive the related PG pin
information.
To guide the tool, use the set_attribute command to set the
related_power_pin_hint and related_ground_pin_hint attributes on the pins
with the missing information.
icc2_lm_shell> set_attribute [get_lib_pins lib/cell/pin] \
related_power_pin_hint PGpin_name

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-49
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

If the related PG pin information for a pin exists but is incorrect, you can correct it by
using the set_attribute command to set the related_power_pin_name,
related_ground_pin_name, or related_bias_pin_name attribute. For example,
icc2_lm_shell> set_attribute [get_lib_pins lib/cell/pin] \
related_power_pin_name PGpin_name

Note:
You can ignore missing power and ground relationships during the workspace
validation by setting the lib.workspace.allow_missing_related_pg_pins
application option to true before running the check_workspace command. However,
the missing information might affect analysis performed by the IC Compiler II tool.
• Pin order
For each cell, the tool determines the pin order in each logic and physical library that
contains the cell, and verifies that it is the same in each library.
In a logic library, the tool determines the pin order from the logic function, followed by
other non-signal pins, such as internal pins, power pins, ground pins, p-well pins, and
n-well pins. In a physical library, the pin order is determined by the order in which they
are specified.
Note:
Although the tool can resolve many pin ordering issues, these issues might be
caused by out-of-date libraries. If the tool reports pin ordering issues, you should
verify that you are using the correct set of libraries before continuing.
If the pin order differs between a logic library and the base library, the result depends on
whether the mismatched pins contribute to the logic function.
❍ If so, the tool issues an error message and does not load the affected cell. You must
manually correct this problem to continue with library preparation.
❍ If not, the tool reorders the pins to match the order in the base library.
If the pin order differs between a physical library and the base library, the tool
automatically updates the pin order using the information from the base library.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-50
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Timing Arc Checks

For each cell with the same name in different logic libraries, the check_workspace
command verifies that the cell has the same timing arcs as those defined in the base library,
including the timing arcs that specify timing constraints, such as setup and hold.
In the following cases, the tool can often resolve the mismatches:
• The libraries use different representations for the same multimode timing arcs.
A multimode timing arc can be represented as a single arc with multiple modes or as
multiple arcs with a single mode. The tool tries to resolve mismatches of multimode arcs
by considering both of these representations.
• The timing arcs use different breakpoints (indexes into the delay lookup table) in the
various logic libraries.
• The breakpoints for complementary attributes (cell_rise and cell_fall,
rise_transition and fall_transition, rise_setup and fall_setup, or rise_hold
and fall_hold) vary within a library or among libraries.
The breakpoints for complimentary attributes must be functions of the same variables,
such as input_net_transition (Tinp) and total_output_net_capacitance (Cout).
However, if one of the attributes is defined as a function of both variables, but the other
is defined as a function of only one variable, the tool can resolve this difference.
The tool can also resolve differences in the complementary attributes for setup or hold
when one attribute is defined as a function of constrained_pin_transition (Tdat) and
the other is defined as a function of related_pin_transition (Tclk).
• A timing arc is represented as a table in one library and as a scalar in another.
• A library is missing rise_transition or fall_transition attributes.
The tool resolves this by setting the unspecified transition time equal to the specified one
for the arcs that are missing these attributes.

If the tool cannot resolve the mismatches, it issues the following message in addition to
messages providing information about the timing arc mismatch.
Error: Could not fix all missing arcs (LM-025)

In the messages, the tool represents a timing arc using the following format:
cell from_pin to_pin [related_pin] sense [object_name] [{w:when_cond}]
[MIN] [{m:modes}] [DUPn]

The cell, from pin, to pin, and arc sense are always specified. The other fields are reported
only when relevant. The related pin is reported only when the delay table is dependent on a
related capacitance. If the library specifies a name for the timing group, that name is
reported in the object_name field. The when_cond field is reported for state-dependent

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-51
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

timing arcs and conditional timing checks. The MIN keyword indicates a minimum delay arc
and the DUP keyword indicates a duplicate arc.
For example, a negative-unate timing arc from pin A to pin Z on the NAND3 cell is
represented as “NAND3 A Z negative_unate”.
To pass workspace validation, you must either fix the errors, provide guidance to the tool
about how to handle them, or remove the cell with mismatched timing arcs from all logic
libraries.
If the tool finds missing or extra timing arcs for a cell in a logic library, as compared to those
in the base library, it issues a warning.
To add arcs that are not defined in the base library, but are defined in another logic library,
rerun the check_workspace command with the -allow_missing option. The arcs are
added only if the nodes in the timing graph are the same as in the base library.
Note:
If you choose to override these errors with the -allow_missing option, the reference
library will have missing data for the cell in some panes.
To remove cells with mismatched timing arcs from the logic libraries, use the
remove_lib_cell command. You must remove the cell from all logic libraries; otherwise,
this results in a missing cell error, which is described in Missing Cell Checks.
For detailed messages during the timing arc checks, specify the arcs_progress keyword
with the -details option. For detailed messages during the breakpoint comparisons,
specify the breakpoint_comparisons keyword with the -details option.
Note:
Using the -details option can result in a very large log file. In general, you should run
the check_workspace command with the -details option only to debug a specific
issue.

Scaling Group Checks

For each scaling group, the check_workspace command verifies that
• Each point on the grid matches exactly one logic library
• The threshold values are the same for all logic libraries in a scaling group
The tool checks the threshold values at both the pin level and the library level. The
threshold values are defined by the following attributes: input_threshold_pct_fall,
input_threshold_pct_rise, output_threshold_pct_fall,
output_threshold_pct_rise, slew_lower_threshold_pct_fall,
slew_lower_threshold_pct_rise, slew_upper_threshold_pct_fall,
slew_upper_threshold_pct_rise, and slew_derate_from_library.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-52
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

If a threshold value is not the same among all the logic libraries in a scaling group, the
tool issues an error message and you cannot commit the workspace.

For detailed messages during the scaling group checks, specify the scaling_group_info
keyword with the -details option.

Leakage-Power Checks
For each cell with the same name in different logic libraries, the check_workspace
command verifies that it has the same leakage-power information, as defined in the
cell_leakage_power attribute and the leakage_power group.

If the tool finds missing or extra leakage-power information for a cell in a logic library, as
compared to those in the base library, it issues a warning. To get detailed information about
the missing leakage-power information, use the -details leakage_progress option when
you run the check_workspace command. In the messages, the tool represents
leakage-power information using the following format:
cell [related_power_pin] [{w:when_condition}]

To add leakage-power information that is not defined in the base library, but is defined in
another logic library, rerun the check_workspace command with the -allow_missing
option.
Note:
If you choose to override this error with the -allow_missing option, the reference library
will have missing data for the cell in some panes.
If the when statement in the leakage_power group is not identical between logic libraries,
the tool checks the logic equivalence of the conditions.
If the conditions are logically equivalent, the tool uses the condition from the base library. If
the conditions are not logically equivalent, the tool issues an error message and you cannot
commit the workspace.

Allowing Incomplete or Inconsistent Library Data

By default, the check_workspace command performs the checks described in Validating the
Workspace. If a library workspace passes these checks, you can commit the workspace to
create a reference library; otherwise, you must fix the reported errors before you can commit
the workspace.
You can relax the workspace verification to enable the tool to generate a reference library
even if the workspace has certain types of incomplete or inconsistent library data by defining
a mismatch configuration. A mismatch configuration specifies the types of workspace
verification errors that can be ignored or fixed by the tool. Reference libraries generated with

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-53
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

this relaxed verification are called prototype libraries; they can be used only for preroute
feasibility analysis.
The library manager provides two predefined mismatch configurations:
• default (the default)
This is the default behavior of the workspace validation and must be used to generate
reference libraries that can be used throughout the implementation flow.
• auto_fix
This mismatch configuration enables the check_workspace command to repair the
mismatches for all of the supported error types, which are shown in Table 2-5.
Table 2-5 Mismatch Configuration Error Types

Error type Description

lib_cell_name_case Cell name mismatch due to case-sensitivity.

Supported repairs:
• record_lib_cell_name_case_ Enables case-insensitivity when comparing cell names.
insensitivity Uses the cell name from the base library.

lib_missing_logical_port Logic library cell is missing a signal port that exists in the
base logic library or physical library.
Supported repairs:
• create_placeholder_logic_ Creates a placeholder port on the logic library cell.
lib_port

lib_missing_physical_port Physical library cell is missing a port that exists in the

base logic library.
Supported repairs:
• create_placeholder_ Creates a placeholder port on the physical library cell.
physical_lib_port The placeholder port is added on the M1 layer with a
location of (0, 0). The terminal width and height are both
equal to the minimum width defined for the M1 layer.

lib_missing_physical_reference A cell exists in the logic libraries, but not in any physical
Supported repairs: libraries.

• create_placeholder_physical
_lib_cell Creates a placeholder physical cell that has the same
dimensions as the LEF unit site and the same number of
ports as the cell in the logic libraries, but no real physical
information.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-54
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-5 Mismatch Configuration Error Types (Continued)

Error type Description

lib_missing_rail_pg Logic library cell is missing a signal port that exists in the
base logic library or physical library.
Supported repairs:
• create_pg_for_rail Creates a placeholder port on the logic library cell.

lib_port_name_case Pin name mismatch due to case-sensitivity.

Supported repairs:
• record_lib_port_name_case_ Enables case-insensitivity when comparing pin names.
insensitivity Uses the pin name from the base library.

lib_port_direction A library cell pin has a different direction than in the base
library.
Supported repairs: Uses the pin direction from the base library in the case of
• change_lib_port_direction signal pin mismatches. Uses the pin direction from the
physical library in the case of PG pin mismatches.
Note:
The library manager fixes many types of pin direction
mismatches by default. For details, see Pin Definition
Checks.

lib_port_type A library cell pin has a different type than in the base
library.
Supported repairs: Uses the pin type from the base library in the case of
• change_lib_port_type signal pin mismatches. Uses the pin type from the
physical library in the case of PG pin mismatches.
Note:
The library manager fixes many types of pin type
mismatches by default. For details, see Pin Definition
Checks.

If these predefined configurations do not meet your needs, you can define your own
configuration, as described in Creating a Mismatch Configuration.
To set a mismatch configuration, use the set_current_mismatch_config command, as
described in Setting a Mismatch Configuration. To see the mismatches that were identified
and fixed during the check_workspace command, use the report_design_mismatch
command after validating the workspace.

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-55
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Creating a Mismatch Configuration

To create a mismatch configuration,
1. Create the configuration by using the create_mismatch_config command.
By default, when you create a user-defined mismatch configuration, it is based on the
default mismatch configuration, and all of the error types are treated as error conditions.
To specify a different mismatch configuration as the basis for the user-defined
configuration, use the -ref_config option.
2. Specify how to handle a specific error type by setting its action attribute for the
configuration.
Specify one of the following values for the action attribute: accept, error, ignore, or
repair. The initial setting of this attribute comes from the reference configuration used
to create the user-defined configuration.
To determine the available error types, use the get_mismatch_types command.
3. If you set the action attribute to repair, specify the repair process to use by setting the
error type’s current_repair attribute for the configuration.
To determine the available repairs for an error type, query the available_repairs
attribute of the error type. Table 2-5 describes many of the error types and their available
repairs.

For example, the following commands create a user-defined mismatch configuration named
user_def that repairs missing physical library cells.
icc2_lm_shell> create_mismatch_config user_def
icc2_lm_shell> set_attribute \
[get_mismatch_types lib_missing_physical_reference] \
action(user_def) repair
icc2_lm_shell> set_attribute \
[get_mismatch_types lib_missing_physical_reference] \
current_repair(user_def) create_placeholder_physical_lib_cell

See Also
• Setting a Mismatch Configuration
• Reporting Mismatch Configurations

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-56
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Setting a Mismatch Configuration

By default, the library manager uses the default mismatch configuration. To set a different
mismatch configuration, use the set_current_mismatch_config command. You can
specify one of the predefined mismatch configurations (default or auto_fix) or a
user-defined mismatch configuration.
For example, to set the mismatch configuration to the predefined auto-fix configuration, use
the following command:
icc2_lm_shell> set_current_mismatch_config auto_fix

To see all available mismatch configurations, use the report_mismatch_configs -all

command.

See Also
• Creating a Mismatch Configuration
• Reporting Mismatch Configurations

Reporting Mismatch Configurations

You can report mismatch configurations by using the commands described in the following
table:

Command Report

get_current_mismatch_config Reports the name of the current mismatch

configuration, such as default or auto_fix.

report_mismatch_configs Reports the details of the current mismatch

configuration.

report_mismatch_configs -all Reports all available mismatch configurations

report_mismatch_configs Restricts the report to specific mismatch

-config_list list configurations.

In the following example, the tool reports the details of the current mismatch configuration,
including the mismatch error types and repair strategies. The report includes mismatch error

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-57
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

types that apply to both the library manager and the implementation tool; only the error types
with a category of library apply to the library preparation process.
icc2_lm_shell> report_mismatch_configs
****************************************
Report : Reporting Mismatch Configs
****************************************

Config : default
-------------------------------------------------------------------------
------------
Mismatch-Type Category Action Allowed Actions
Strategy Available Strategies
-------------------------------------------------------------------------
------------
lib_missing_physical_reference
library error {repair error accept }
null
{create_placeholder_physical_lib_cell }
lib_missing_logical_port
library error {repair error accept }
null {create_placeholder_logic_lib_port
}
lib_missing_physical_port
library error {repair error accept }
null {create_placeholder_physical_lib_po
rt }
lib_port_type library accept {accept }
change_lib_port_type
{change_lib_port_type }
lib_port_direction
library accept {accept }
change_lib_port_direction
{change_lib_port_direction }
lib_port_name_synonym
library ignore {repair accept ignore }
null {record_lib_port_name_synonym }
...
lib_cell_name_case
library ignore {repair accept ignore }
null
{record_lib_cell_name_case_insensitivity }
lib_port_name_case
library ignore {repair accept ignore }
null {record_lib_port_name_case_insensit
ivity }
lib_missing_rail_pg
library ignore {repair accept ignore }
null {create_pg_for_rail }
...
1

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-58
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

See Also
• Creating a Mismatch Configuration
• Setting a Mismatch Configuration

Generating Frame Views

If a library workspace passes validation, the check_workspace command creates frame
views for the blocks in the workspace. You do not need to run a separate command to create
the frame views.
The IC Compiler II Library Manager tool uses the lib.physical_model application options
to control the frame view generation. You must set these application options before running
the check_workspace command. When you commit the workspace, the library manager
saves these application option settings with the reference library.
To update frame views for an existing reference library, such as when the technology file or
tool version is updated, use the process described in Modifying a Reference Library.

See Also
• Building Reference Libraries
• Frame View Generation Application Options

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-59
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Identifying Secondary PG Pins

The router uses the is_secondary_pg attribute to identify the PG and bias pins on which to
perform secondary PG pin routing. The check_workspace command sets this attribute on
the pins based on certain pin and block attribute settings.
• For PG pins, the setting is based on the pg_type and std_cell_main_rail attributes of
the PG pin, which are defined in the logic library source files, and the design_type
attribute of the block, which is derived from the physical library source files. Table 2-6
shows the is_secondary_pg settings for the various combinations of these attributes.
• For bias pins, the setting is based on the pg_type and physical_connection attributes
of the bias pin, which are defined in the logic library source files. Table 2-7 shows the
is_secondary_pg settings for the various combinations of these attributes.
Table 2-6 Determining the is_secondary_pg Setting for PG Pins

Reference library Reference library

Logic library PG pin attribute cell attribute pin attribute

pg_type std_cell_main_rail design_type is_secondary_pg

primary_power true all false

or
primary_ground

primary_power false or unset all true

or
primary_ground

backup_power or any value all true

backup_ground

Table 2-7 Determining the is_secondary_pg Setting for Bias Pins

Logic library PG pin attribute Reference library pin attribute

pg_type physical_connection is_secondary_pg

pwell, nwell, routing_pin true

deeppwell, or
deepnwell

pwell, nwell, device_layer false

deeppwell, or
deepnwell

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-60
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Committing the Workspace

After the workspace passes validation with the check_workspace command, you can
commit the workspace, which saves the workspace on-disk as a reference library. To
commit the workspace, use the commit_workspace command. By default, the tool saves
the reference library in the current directory using the name workspace_name.ndm using
the current schema revision.
icc2_lm_shell> commit_workspace

To override the default behavior, use the following options:

• -output file_name
This option saves the reference library with the specified file name. For example, to save
the reference library in a file named myreflib.ndm, use the following command:
icc2_lm_shell> commit_workspace -output myreflib.ndm

Note that this option also changes the name of the reference library.
• -version version_string
This option saves the reference library using the schema revision for an older tool
version. To see the available version strings, use the report_versions command.

By default, the command fails if the specified reference library already exists. To overwrite
an existing reference library, use the -force option. For example,
icc2_lm_shell> commit_workspace -output myreflib.ndm
Error: File 'myreflib.ndm' already exists (FILE-009)
icc2_lm_shell> commit_workspace -force -output myreflib.ndm

To enable all commit_workspace commands to overwrite an existing reference library

without using the -force option, set the
lib.workspace.allow_commit_workspace_overwrite application option to true.
icc2_lm_shell> set_app_options \
-name lib.workspace.allow_commit_workspace_overwrite -value true

The views saved in the generated reference library depend on the library preparation flow
you enabled and the settings of the related application options.
• For the normal and ETM library preparation flows, the timing and frame views are saved
• For the frame-only and physical-only library preparation flows, only the frame views are
saved

Chapter 2: Preparing Reference Libraries

Building Reference Libraries 2-61
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• To save the design views, set the lib.workspace.save_design_views application

option to true.
• To save the layout views, set the lib.workspace.save_layout_views application
option to true.

You can have only a single workspace in memory at one time. After you commit a
workspace, it is removed from memory so that you can prepare another reference library.

See Also
• Library Preparation Flows

Using the Exploration Flow

The exploration flow automatically analyzes your library source files and generates a script
that you can use to create a reference library.
To use the exploration flow to build a reference library,
1. Define the search path, as described in Defining the Search Path.
2. Create the root library workspace for the exploration flow, as described in Creating a
Library Workspace.
3. Load the logic library source files into the root workspace, as described in Loading the
Logic Libraries.
4. Load the physical library source files into the root workspace, as described in Loading
the Physical Libraries.
5. (Optional) Enable scaling group creation, as described in Enabling Scaling Group
Creation.
6. Analyze the library source files to automatically create the subworkspaces, as described
in Performing Automated Library Analysis.
7. (Optional) Edit the subworkspaces.
8. (Optional) Enable aggregate library creation.
To create an aggregate library from the subworkspaces, set the
lib.workspace.explore_create_aggregate application option to true. For
information about aggregate libraries, see Creating an Aggregate Library.

Chapter 2: Preparing Reference Libraries

Using the Exploration Flow 2-62
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

9. Validate the library workspace and commit it to disk.

You can use either of the following methods to validate and commit the library workspace
when you use the exploration flow:
❍ Validate and commit the exploration flow library workspace by running the
process_workspaces command on it.
When you run this command, the tool validates each subworkspace in the root
workspace and, if the workspace passes validation, commits it to a reference library.
This command performs the same functions on each subworkspace as the
check_workspace and commit_workspace commands, but uses less peak memory
when processing multiple subworkspaces.
For more information about workspace validation, see Validating the Workspace. To
specify validation options for the process_workspaces command, use the
-check_options option.
For more information about committing a workspace, see Committing the Workspace.
The process_workspaces command accepts the same options as the
commit_workspace command to control the commit process.

❍ Generate a library preparation script and source it to create the reference library, as
described in Using a Library Preparation Script.

To reduce the runtime of the exploration flow, use the fast exploration flow, as described in
Using the Fast Exploration Flow.

Enabling Scaling Group Creation

By default, the exploration flow does not create scaling groups for the logic libraries;
however, the group_libs command issues the following message if it determines that
scaling groups could be created:
Information: Identified a potential valid scaling group. (LM-027)

To enable scaling group creation, set the lib.workspace.group_libs_create_slg

application option to true before running the group_libs command.
icc2_lm_shell> set_app_options \
-name lib.workspace.group_libs_create_slg -value true

See Also
• Creating Scaling Groups
• Performing Automated Library Analysis

Chapter 2: Preparing Reference Libraries

Using the Exploration Flow 2-63
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Performing Automated Library Analysis

To analyze the library source files in the root workspace and partition them into a set of
subworkspaces, use the group_libs command.
icc2_lm_shell> group_libs

This command partitions the library source files into subworkspaces based on the names of
the library cells. It analyzes the logic libraries to identify both single-cell and multiple-cell
logic libraries. The group_libs command checks only the library cell names; it does not
check the pins, function, or timing arcs of the library cells.
For each subworkspace, the group_libs command adds the physical libraries that include
at least the same set of cells. If the physical libraries contain cells that are not in any of the
logic libraries, the group_libs command also creates a physical-only subworkspace.
By default, the group_libs command
• Checks for cell shadowing across subworkspaces, and fixes any detected issues
Cell shadowing occurs when a library cell with the same name exists in multiple
reference libraries. In this case, the tool uses the data from the first reference library in
which it finds the cell, and it ignores that cell’s data in all other reference libraries.
By default, the group_libs command adjusts the grouping such that each cell exists in
only one generated reference library, which includes all the PVT panes for the cell. To
disable these fixes, set the lib.workspace.group_libs_fix_cell_shadowing
application option to false.
• Tries to put as many macro cells as possible into a single subworkspace
When using this strategy, the command groups all macro cells with the same set of
characterization points into a single subworkspace. This strategy creates the smallest
number of subworkspaces.
To create subworkspaces that each contain a single macro cell with all of its
characterization points, set the
lib.workspace.group_libs_macro_grouping_strategy application option to
single_cell_per_lib before running the group_libs command. Using this strategy
can generate a large number of subworkspaces.
• Assigns a name of <root_workspace>_physical_only to the physical-only subworkspace,
if there is one
To specify a name for the physical-only subworkspace, set the
lib.workspace.group_libs_physical_only_name application option.

Chapter 2: Preparing Reference Libraries

Using the Exploration Flow 2-64
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

• Assigns names to the other subworkspaces by using a unique combination of logic

library prefix and suffix characters
To enable other naming strategies, set the
lib.workspace.group_libs_naming_strategies application option.
To report the names of the subworkspaces, use the get_workspaces command. To
change a workspace name, use the rename_workspace command.
Note:
If you change the set of source libraries in the root workspace or change the contents of
any library in the root workspace, you must rerun the group_libs command to re-create
the subworkspaces; otherwise, the subworkspaces might contain obsolete data.

Using a Library Preparation Script

When you use the exploration flow, the tool can generate a library preparation script to
create the reference libraries. The generated script file performs the following tasks for each
workspace:
1. Creates the library workspace.
2. Loads the logic and physical library source files into the library workspace.
3. Creates scaling groups for the logic libraries, if enabled.
4. Validates the contents of the library workspace.
5. Commits the library workspace to disk using the name of the first logic library as the
reference library name.

In addition, if you enable aggregate library creation by setting the

lib.workspace.explore_create_aggregate application option to true, the script
creates an aggregate library that contains the reference libraries generated for the
workspaces.
Note:
The generated script file also includes any set_app_options and reset_app_options
commands issued in the icc2_lm_shell session before running the write_workspace
command.

Chapter 2: Preparing Reference Libraries

Using the Exploration Flow 2-65
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

To use this method to create the reference libraries,

1. Generate the library preparation script by using the write_workspace command.
When you run this command, you must specify how to output the script:
❍ Generate one script file per workspace
To write one script file per workspace, use the -directory option to specify the
directory in which to save the script files. The tool names each script file
workspace_name.tcl. For example, to save the script files in a directory named
libgen_scripts, use the following command:
icc2_lm_shell> write_workspace -directory libgen_scripts

❍ Generate one script file for all workspaces

To generate a single script file, use the -file option to specify the file name. For
example, to save the script in a file named libgen.tcl, use the following command:
icc2_lm_shell> write_workspace -file libgen.tcl

The default behavior of this command depends on the current workspace. If the current
workspace is the root workspace, it generates a script for each subworkspace. If the
current workspace is a subworkspace, it generates a script only for that workspace. To
generate a script for specific workspaces, specify the workspaces as an argument to the
command. For example, to generate a Tcl script only for the my_lib workspace, use the
following command:
icc2_lm_shell> write_workspace -file libgen.tcl my_lib

You should review the generated script files, and modify as necessary to ensure that it
meets your needs before using it to perform your library preparation.
2. Remove the existing root workspace, which also removes all of its subworkspaces, by
using the remove_workspace command.
icc2_lm_shell> remove_workspace

3. Create the reference libraries by sourcing the generated script.

icc2_lm_shell> source file_name

If the check_workspace command reports any issues, you must resolve the issues and
rerun the script. For information about resolving the issues, see Validating the
Workspace. In addition, you might need to modify the generated script to resolve some
issues.

Chapter 2: Preparing Reference Libraries

Using the Exploration Flow 2-66
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Using the Fast Exploration Flow

The fast exploration flow reduces the runtime required for the exploration flow by up to 50X
by loading only the information required for library analysis by the group_libs command.
To enable this flow, set the lib.workspace.fast_exploration application option to true
before loading the logic libraries.
When you use the fast exploration flow, you cannot use the process_workspaces
command to check and commit the workspaces. Instead, you must use the
write_workspace command to create a library preparation script and source this script to
create the reference libraries.
The following script shows the commands used in the fast exploration flow:
set_app_options -name lib.workspace.fast_exploration -value true
read_db {my_db_files}
group_libs
write_workspace -file libprep.tcl
remove_workspace
source libprep.tcl

See Also
• Performing Automated Library Analysis
• Using a Library Preparation Script

Verifying Reference Libraries

The IC Compiler II library manager provide a verification flow to validate the logical
information or frame views of a reference library. You can use this flow to
• Compare the logical information in a logic library source file and an existing reference
library, as described in Verifying Logical Information in a Reference Library.
• Compare the frame views in two reference libraries. The reference libraries can be
complete libraries or frame-only libraries, as described in Verifying the Frame Views in a
Reference Library.

Chapter 2: Preparing Reference Libraries

Verifying Reference Libraries 2-67
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Verifying Logical Information in a Reference Library

The library manager can verify that the following objects are the same in a reference library
and a logic library source file:
• The library-level attributes
• The cells
• The pin information, timing arcs, and power data for each cell
To verify the logical information in a reference library,
1. Open the reference library in a verification workspace by using the create_workspace
-flow verification command.
icc2_lm_shell> create_workspace -flow verification mylib.ndm

The reference library opened in the verification workspace is referred to as the base
library.
2. Compare the logical information in a logic library source file to the reference library in the
library workspace by using the compare_db command.
icc2_lm_shell> compare_db -process_label myprocess mylib.db

The logic library source file is referred to as the comparison library.

The compare_db command uses the following tests to identify the pane (logic library) in
the base library to compare to the comparison library:
❍ An exact match between the name of the comparison library and the source file used
to generate a pane in the base library
❍ A matching pane based on process label, process number, temperature, and voltage
To see the panes in the base library, use the report_workspace -panes command.
If the compare_db command cannot find a matching pane, the comparison fails. If it finds
a matching pane, it performs the comparison and reports any differences.
3. When you have finished verifying the reference library, remove the library workspace by
using the remove_workspace command.

Chapter 2: Preparing Reference Libraries

Verifying Reference Libraries 2-68
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Verifying the Frame Views in a Reference Library

The library manager can verify that the frame views are the same in two reference libraries
by comparing the following information:
• The schema version
• The default site
• The number of frame views
• For each frame view, the design type, boundary, port information, number of terminals,
terminal colors, existence of access edges, and via region contact codes
To verify the frame views in a reference library,
1. Open the reference library in a verification workspace by using the create_workspace
-flow verification command.
icc2_lm_shell> create_workspace -flow verification mylib1.ndm

The reference library opened in the verification workspace is referred to as the base
library.
2. Compare the frame views in another reference library to the reference library in the
library workspace by using the compare_ndm command.
icc2_lm_shell> compare_ndm mylib2.ndm

The reference library opened by the compare_ndm command is referred to as the

comparison library.
3. When you have finished verifying the reference library, remove the library workspace by
using the remove_workspace command.

Chapter 2: Preparing Reference Libraries

Verifying Reference Libraries 2-69
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Modifying a Reference Library

You can modify the technology data and physical cell data, but not functional cell data, for
an existing reference library.
To modify a reference library,
1. Define the search path by setting the search_path variable, as described in Defining the
Search Path.
2. Create a library workspace for the edit flow by using the create_workspace command,
as described in Creating a Library Workspace.
For example, to modify the reference library stored in the my_ref.ndm file, use the
following command:
icc2_lm_shell> create_workspace my_ref.ndm -flow edit

3. Modify the reference library by performing one or more of the following tasks:
❍ Load new technology data, as described in Loading the Technology Data.
❍ Modify the technology data, as described in Completing the Technology Data.
❍ Load physical library source files into the library workspace, as described in Loading
the Physical Libraries.
❍ Load a reference library into the library workspace by using the read_ndm command,
as described in Loading Physical Data from a Reference Library.
Note:
When you load a reference library into an edit workspace, only the physical
information is loaded; the timing information is not used.
❍ Modify physical cell attributes.
In general, you can modify physical cell attributes by using the set_attribute
command. For examples of this technique, see Completing the Physical Cell
Information.
❍ Define antenna properties, as described in Defining Antenna Properties on Standard
Cells and Defining Antenna Properties on Hard Macro Cells.
❍ Edit the layout for one or more cells, as described in the IC Compiler II Graphical User
Interface User Guide.
4. Validate the contents of the library workspace by using the check_workspace command,
as described in Validating the Workspace.
When you validate the library workspace, the tool checks only the modified physical
data. By default, the tool generates updated frame views only for cells with modified

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-70
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

design views. To generate a frame view for a cell whose design view is unchanged, set
the frame_update attribute on the cell to true before running the check_workspace
command.
If you want to use the same frame generation options that were used when the reference
library was created, use the write_frame_options command to generate a Tcl script
with the application option settings, and source this script before running the
check_workspace command.

5. Commit the library workspace to disk by using the commit_workspace command, as

described in Committing the Workspace.

For example, the following script updates the technology file for an existing reference library
named existing.ndm and regenerates the frame views for all of the design views using the
same application option settings that were used to generate the reference library:
write_frame_options -library existing.ndm -output frame_options.tcl
create_workspace –flow edit existing.ndm
read_tech_file new_tech.tf
set_attribute [get_lib_cells */*/design] frame_update true
source frame_options.tcl
check_workspace
commit_workspace -force -output existing.ndm

Defining Antenna Properties on Standard Cells

The IC Compiler II tool uses antenna properties annotated on the frame view of the standard
cells to perform antenna checking and fixing.
If the LEF file defines these antenna properties for the standard cells, they are automatically
annotated on the frame view of the cells when you generate the reference library. Otherwise,
you must use the edit flow to annotate these properties on the standard cells after
generating the reference library.
To annotate antenna properties on a standard cell,
1. Open the reference library in edit mode as described in Modifying a Reference Library.
2. Use one of the following methods to set the antenna property attributes:
❍ Use the set_attribute command to set the attributes directly.
❍ Use the read_clf_antenna_properties command to set the attributes by reading
a Cell Library Format (CLF) file.
For information about the antenna property attributes for standard cells, see Antenna
Properties for Standard Cells.

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-71
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

3. Validate the contents of the library workspace by using the check_workspace command,
as described in Validating the Workspace.
4. Commit the library workspace to disk by using the commit_workspace command, as
described in Committing the Workspace.

Antenna Properties for Standard Cells

A standard cell has antenna properties that define the gate and antenna areas of its input
pins, diode protection value of its output pins, and whether a pin can be used as a diode.
These settings are represented by attributes on the cell pins. You can set these attributes
directly with the set_attribute command or set them by reading a CLF file with the
read_clf_antenna_properties command.
Table 2-8 Standard Cell Antenna Property Attributes

Attribute Description

gate_area This attribute defines the gate area of an input pin.

• If the library supports a single gate oxide mode, the attribute value
uses the following syntax:
{ {layer_name area_value} ... }

• If the library supports multiple gate oxide modes, the attribute

value uses the following syntax:
{ {oxide_mode layer_name area_value} ... }

Note:
If this attribute is not specified for a pin, the IC Compiler II tool uses
the setting of the route.detail.default_gate_size application
option.

antenna_area These attributes define the antenna area of an input pin. The
antenna_area attribute defines the antenna polygon area. The
antenna_side_area
antenna_side_area attribute defines the antenna sidewall area.
The attribute values use the following syntax:
{layer_name area_value}

Note:
If these attributes are not specified for a pin, the IC Compiler II tool
uses the pin shapes to compute the antenna area.

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-72
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-8 Standard Cell Antenna Property Attributes (Continued)

Attribute Description

diff_area This attribute defines the diode protection value of an output pin.
The attribute value uses the following syntax:
{layer_name area_value}

Note:
If this attribute is not specified for a pin, the IC Compiler II tool uses
the setting of the route.detail.default_diode_protection
application option.

is_diode This attribute specifies whether a pin is a diode that can be used by
the IC Compiler II tool to fix antenna violations.

Defining Antenna Properties on Hard Macro Cells

The IC Compiler II tool uses antenna properties annotated on the frame view of the hard
macro cells to perform antenna checking.
If you enable IC Validator antenna extraction during library validation, as described in
Automatic Antenna Property Extraction Using the IC Validator Tool, these properties are
automatically annotated on the frame view of the cells when you generate the reference
library. Otherwise, you must use the edit flow to annotate these properties on the hard macro
cells after generating the reference library.
To annotate antenna properties on a hard macro,
1. Open the reference library in edit mode as described in Modifying a Reference Library.
2. Use one of the following methods to set the antenna property attributes:
❍ Use the set_attribute and set_port_antenna_property commands to set the
attributes directly.
❍ Use the read_clf_antenna_properties command to set the attributes by reading
a Cell Library Format (CLF) file.
For information about the antenna property attributes for standard cells, see Antenna
Properties for Hard Macro Cells.
3. Validate the contents of the library workspace by using the check_workspace command,
as described in Validating the Workspace.
4. Commit the library workspace to disk by using the commit_workspace command, as
described in Committing the Workspace.

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-73
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Antenna Properties for Hard Macro Cells

A hard macro cell has antenna properties that define the gate area, antenna area, and
antenna ratio of its input ports and the diode protection value of its output ports. You can set
these attributes directly with the set_attribute and set_port_antenna_property
commands or set them by reading a CLF file with the read_clf_antenna_properties
command.

Setting Hard Macro Antenna Properties Directly

To set the hard macro antenna properties directly,
1. Use the set_attribute command to set the diode protection value (diff_area
attribute) on the hard macro output ports.
Use the following syntax to specify this attribute:
{ {layer_name area_value} ... }

For example,
icc2_lm_shell> set_attribute mylib/hm1/z diff_area \
{M1 0 M2 0 M3 0 M4 0.0595}

2. Use the set_port_antenna_property command to set the gate area, antenna area,
and antenna ratio properties on the hard macro input ports. This command has the
following syntax:
set_port_antenna_property -port port -data property_settings_list

In the property_settings_list argument, specify the properties for one or more layers
using the following syntax:
{ {metalLayer layer_name gate_size area_value mode1_area mode1_data
mode2_ratio mode2_data mode3_area mode3_data mode4_area mode4_data
mode5_ratio mode5_data mode6_area mode6_data} ... }

where
❍ layer_name is the name of the metal layer in the technology file

❍ area_value is the gate area of the port on the specified layer

❍ mode1_data is the area of the specified metal layer when the connectivity is traced up
to that metal layer
❍ mode2_data is the maximum internal ratio of the area of the metal layer below the
specified metal layer when the connectivity is traced up to the specified metal layer
❍ mode3_data is the total metal area

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-74
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

❍ mode4_data is the sidewall area of the specified metal layer when the connectivity is
traced up to the specified metal layer
❍ mode5_data is the maximum internal ratio of the sidewall area of the metal layer
below the specified metal layer when the connectivity is traced up to the specified
metal layer
❍ mode6_data is the total metal sidewall area
The library manager also supports a simplified syntax that excludes the property names:
{ {layer_name area_value mode1_data mode2_data mode3_data
mode4_data mode5_data mode6_data} ... }

For example, you can use either of the following commands to set the antenna properties
on the a pin of the hm1 hard macro cell:
icc2_lm_shell> set_port_antenna_property -port mylib/hm1/a -data \
{ {metalLayer M1 gate_size 0.3436 mode1_area 6.664
mode2_ratio 2.05346 mode3_area 12.708 mode4_area 17.5392
mode5_ratio 7.04044 mode6_area 12.682}
{metalLayer V1 gate_size 0.3436 mode1_area 6.664
mode2_ratio 2.05346 mode3_area 12.708 mode4_area 17.5392
mode5_ratio 7.04044 mode6_area 12.682} }

or
icc2_lm_shell> set_port_antenna_property -port mylib/hm1/a -data \
{ {M1 0.3436 6.664 2.05346 12.708 17.5392 7.04044 12.682}
{V1 0.3436 6.664 2.05346 12.708 17.5392 7.04044 12.682} }

Note:
For the layer below the pin layer, set the hierarchical antenna properties to 0. Also, if
the gate_size value for a metal layer is zero, such as for an output pin, the
mode2_ratio and mode5_ratio values for that layer must be 0.

Chapter 2: Preparing Reference Libraries

Modifying a Reference Library 2-75
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Creating an Aggregate Library

An aggregate library is grouping of multiple reference libraries into a single reference library
for easier maintenance and distribution.
To create an aggregate library,
1. Define the search path, as described in Defining the Search Path.
2. Create a library workspace for the aggregate flow, as described in Creating a Library
Workspace.
When you create the library workspace, specify the aggregate library name as the
workspace name. For example, to create an aggregate library named my_agg, use the
following command:
icc2_lm_shell> create_workspace my_agg -flow aggregate

3. Load the reference libraries into the library workspace, as described in Opening a
Reference Library.
All of the reference libraries in the library workspace become part of the aggregate
library. To remove libraries from the workspace, use the remove_lib command.
4. Validate the contents of the library workspace, as described in Validating the Workspace.
5. Set the search order, as described in Setting the Search Order.
6. Commit the library workspace to disk, as described in Committing the Workspace.

See Also
• Aggregate Library
• Modifying an Aggregate Library

Setting the Search Order

The search order specifies the order in which to search the reference libraries comprising
the aggregate library when resolving a cell reference.
To specify the search order, use the set_lib_order command to list the reference libraries
in the order in which to look for files. When the IC Compiler II tool resolves a cell reference,
it starts searching in the leftmost reference library in the list and uses the first matching cell
it finds.

Chapter 2: Preparing Reference Libraries

Creating an Aggregate Library 2-76
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Modifying an Aggregate Library

To modify an aggregate library,
1. Define the search path, as described in Defining the Search Path.
2. Create a library workspace for the edit flow, as described in Creating a Library
Workspace.
When you create the library workspace, specify the existing library file name as the
workspace name. For example, to modify the aggregate library stored in the
my_agg.ndm file, use the following command:
icc2_lm_shell> create_workspace my_agg.ndm -flow edit

3. Adjust the reference libraries in the library workspace.

When you create a library workspace for an existing aggregate library, its reference
libraries are automatically opened in the library workspace. To see the reference libraries
in the workspace, use the get_libs or report_workspace command.
To change the search order of the reference libraries, set the search order, as described
in Setting the Search Order.
To add reference libraries to the library workspace, open the libraries, as described in
Opening a Reference Library.
To remove reference libraries from the library workspace, close the libraries, as
described in Closing a Reference Library.
4. Validate the contents of the library workspace, as described in Validating the Workspace.
5. Set the search order, as described in Setting the Search Order.
6. Commit the library workspace to disk, as described in Committing the Workspace.

See Also
• Creating an Aggregate Library

Chapter 2: Preparing Reference Libraries

Modifying an Aggregate Library 2-77
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Opening a Reference Library

You can open a reference library outside of a library workspace to query or view the
contents of the reference library. To open a reference library outside of a library workspace,
use the open_lib command.
Note:
To load a reference library into a library workspace, use the read_ndm command, as
described in Loading Physical Data from a Reference Library.
For example, to open the myreflib reference library, use the following command:
icc2_lm_shell> open_lib myreflib.ndm

Each time you run the command, you can specify only a single reference library file to open;
to open multiple reference libraries, you must run the command multiple times.
You can specify the reference library file with an absolute path, a relative path, or no path. If
you specify the file with a relative path or with no path, the tool uses the search path to find
the file.

See Also
• Defining the Search Path

Getting Information About Reference Libraries

You can report information about the reference libraries and their contents. To learn about
these reporting capabilities, see
• Querying Libraries
• Reporting Libraries
• Reporting the Frame Properties
• Querying Library Objects
• Reporting Library Objects

Chapter 2: Preparing Reference Libraries

Opening a Reference Library 2-78
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Querying Libraries
To list the libraries loaded into memory, use the get_libs command.
icc2_lm_shell> get_libs
{myreflib myreflib_lvt myreflib_hvt}

If you have opened an aggregate library, the get_libs command returns the reference
libraries within the aggregate library. The reference library names are prefixed with the
aggregate library name.
icc2_lm_shell> get_libs
{AGG1|reflib1 AGG1|reflib2}

You can specify a pattern to restrict the set of libraries. For example, to include only the low
threshold voltage libraries, enter the following command:
icc2_lm_shell> get_libs *lvt
{myreflib_lvt}

Reporting Libraries
To report information about a reference library, use the report_lib command. You must
specify the name of an open reference library as an argument. You can run this command
both before and after committing the library workspace.
By default, this command provides information about the library, such as the number of cells,
the power rails, the characterization points (panes), and the operating condition definitions.
Use the following options to report additional information about the reference library:
• -antenna
Reports the library cells that are missing antenna properties and the affected pins.
• -parasitic_tech
Reports the TLUPlus files loaded into the library, if any.
• -physical
Reports the physical characteristics of the reference library.
The reported information includes the site definitions, the layer definitions, the source file
names, the number of each type of cell view (timing, layout, design, and frame) in the
library, the number of each design type in the library, details about each library cell, the
number of each type of library cell pin (ground, power, and signal) in the library, and
details about the pins for each library cell.

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-79
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• -placement_constraints
Reports missing or improper placement constraints.
Reported issues include improper site definitions and library cells that do not have any
shapes on the placement layers defined in the technology file, such as implant and
diffusion layers. By default, the report includes a maximum of 10 cells with violations. To
report all cells with violations, use the -verbose option.
• -routability
Reports library issues that could impact the routability.
Reported issues include library cell pins that do not have either a via region or access
edges, irregular cut shapes or routing blockages, frame views that are converted from
IC Compiler FRAM views, improper frame generation settings, frame views with many
obstructions, shorted pins, routing ports without geometry information, ports whose
is_secondary_pg or is_diode attribute differs between the timing view and the frame
view, and fully blocked terminals.
To report details about the cell objects, such as the number of terminals, shapes, and
routing blockages, and to report both fully and partially blocked terminals, use the
-verbose option.

• -timing_arcs
Reports the timing arcs for the library cells.
• -wire_tracks
Reports library issues related to the wire tracks.
Reported issues include cells with off-track or missing via regions and layers without a
preferred direction. By default, the report includes the name and layer for each violating
library cell pin, as well as the issue causing the violation. To report additional details for
the violating library cell pins such as the contact code and bounding box, use the
-verbose option.
By default, the library manager determines the wire tracks from the library being
reported. If the wire track information is stored in a technology library, use the
-technology_lib option to specify the library.

• -wire_track_colors
Reports library issues related to wire track coloring.
Reported issues include tracks without color information, terminals without color
information, and terminals on a track with the incorrect color.
• -min_pin_layer layer
Reports terminals on layers lower than the specified pin layer.

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-80
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Example 2-5 shows an example of the default reference library report.

Example 2-5 Reference Library Report
icc2_lm_shell> report_lib myreflib
****************************************
Report : library
Library: myreflib
****************************************

Full name: /usr/libs/myreflib.ndm:myreflib

File name: /usr/libs/myreflib.ndm
Lib type: cell
Design count: 434
Timing data:

Power rails:

Index Name Type

0 <default> power
1 V power
2 VL power
3 VSS ground

Pane count: 2

Pane 0:
Process label: (none)
Process number: 1
Voltage rail count: 3
Voltage for rail 0 (<default>): 1.08
Voltage for rail 1 (V): 1.08
Voltage for rail 2 (VL): 1.08
Temperature: 125

Thresholds:
r/f InputDelay: 0.5/0.5 r/f OutputDelay: 0.5/0.5
l/h RiseTrans: 0.1/0.9 h/l FallTrans: 0.9/0.1
TransDerate: 1

Source .db file:

/usr/libs//DB/myreflib_125c.db
Pane 1:
...

Source .db libraries:

myreflib_125c.db:myreflib_125c
myreflib_40c.db:myreflib_40c

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-81
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Operating Conditions:

Name Process Temp Voltage Original DB Name

------------------------------------------------------------------------
WORST 1.00 125.00 1.08 myreflib_max_hth
BEST 1.00 -40.00 1.32 myreflib_min

Reporting the Frame Properties

The library manager extracts frame views of the library cells when you run the
check_workspace command.

To report the frame view properties for one or more library cells, use the
report_frame_properties command. You can run this command only after committing
the library workspace. You must use the -library option to specify the name of an open
reference library and the -output option to specify the name of the output file.
icc2_lm_shell> open_lib myreflib
icc2_lm_shell> report_frame_properties -library [current_lib] \
-output frame.txt

By default, the command reports the frame view properties for all cells in the reference
library. To report the frame view properties for a specific cell, use the -block option to
specify the cell name. Note that when you use this option, you must explicitly specify the
frame view of the cell.
Example 2-6 shows an example frame properties report, which was generated by the
following command:
icc2_lm_shell> report_frame_properties -library [current_lib] \
-output frame.txt -block myreflib/AND2/frame

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-82
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Example 2-6 Frame Properties Report

****************************************
Report : frame properties
Library: myreflib

****************************************
**********************
Design : AND2
**********************
Total number of row: 1.

***** implant_width property *****

No implant width property on this block.

***** diffusion_width_height property *****

No diffusion width height property on this block.

***** source_drain annotation *****

No source/drain annotation on this block.

See Also
• Frame View Generation Application Options

Querying Library Objects

You can query the library cells and library cell pins both before and after committing the
library workspace.
• To determine the library cells available in a library, use the get_lib_cells command.
If you run the command without any arguments, it returns all the timing views in the
current library. If the library does not contain any cells with timing views, the command
returns the frame views, if they exist; otherwise, it returns the design views.
If you specify the library cells, use the following format:
library_name/cell_name[/view]
You must specify both the library name and the cell name. You can specify a pattern,
including wildcards for the library name and cell name. If you specify the view, it must be
one of the following keywords: design, frame, layout, or timing.
For example, to return all the frame views in the myreflib reference library, use the
following command:
icc2_lm_shell> get_lib_cells myreflib/*/frame
{myreflib/AND2/frame myreflib/AND4/frame myreflib/AO21/frame ...}

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-83
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• To determine the pins on a library cell, use the get_lib_pins command.

If you run the command without any arguments, it returns all the library cell pins in the
current library. If you specify the library cells, use the following format:
library_name/cell_name/pin_name
You must specify the library name, the cell name, and the pin name. You can specify a
pattern, including wildcards for the library name, cell name, and pin name.
For example, to return all the pins of the AND2 cell in the myreflib reference library, use
the following command:
icc2_lm_shell> get_lib_pins myreflib/AND2/*
{myreflib/AND2/IN1 myreflib/AND2/IN2 myreflib/AND2/OUT}

Note:
To reduce runtime when you load physical libraries in the physical-only flow, the tool
loads only the cell names, and not detailed information for the cells. The tool loads the
detailed information during workspace validation. This means that after loading the
physical libraries, you can query the library cell names, but you cannot query other
information such as pins, attributes, and shapes until after workspace validation.
If you need to examine the cells in detail before workspace validation, load the physical
library in the normal flow.

Reporting Library Objects

You can report information about the library cells, library cell pins, and library timing arcs.
You can generate the library cell and library cell pin reports both before and after committing
the library workspace. You can generate the library timing arc report only after committing
the library workspace.
• To report information about one or more library cells, use the report_lib_cells
command. You must use the -objects option to specify the library cells.
Use the following format to specify the library cells: library_name/cell_name. You must
specify both the library name and the cell name. You can specify a pattern, including
wildcards for the library name and cell name.
By default, the report includes the full name, area, pin count, and design type for the
specified cells, as well as whether the cell is sequential.

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-84
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

For example, to report on the AND2 cell in the myreflib reference library, use the
following command:
icc2_lm_shell> report_lib_cells -objects myreflib/AND2
****************************************
Report : lib_cell
****************************************

full_name area pin_count is_sequential design_type

-------------------- ---------- --------- ------------- ------------
myreflib/AND2 11.0005 3 false lib_cell
1

You can customize the report by using the -columns option to specify the information to
report. The following column names are valid for this report: area, design_type,
dont_touch, full_name, is_combinational, is_isolation, is_level_shifter,
is_memory_cell, is_sequential, is_three_state, name, pad_cell, pin_count,
valid_purposes, and view_name. To display all of the available information, specify
-columns all.

• To report information about one or more library cell pins, use the report_lib_pins
command. You must use the -objects option to specify the library cell pins.
Use the following format to specify the library cell pins: library_name/cell_name/
pin_name. You must specify the library name, the cell name, and the pin name. You can
specify a pattern, including wildcards for the library name, cell name, and pin name.
By default, the report includes the full name and direction for the specified pins.
For example, to report on all the pins of the AND2 cell in the myreflib reference library,
use the following command:
icc2_lm_shell> report_lib_pins -objects myreflib/AND2/*
****************************************
Report : lib_pin
****************************************

full_name direction
------------------------- --------
myreflib/AND2/IN1 in
myreflib/AND2/IN2 in
myreflib/AND2/OUT out
1

You can customize the report by using the -columns option to specify the information to
report. The following column names are valid for this report: direction,
disable_timing, full_name, function, is_async_pin, is_clock_pin,
is_data_pin, is_pad, is_preset_pin, is_three_state,
is_three_state_enable_pin, is_three_state_output_pin, name, pin_number,
port_type, rail_name, signal_type, and three_state_function. To display all of
the available information, specify -columns all.

Chapter 2: Preparing Reference Libraries

Getting Information About Reference Libraries 2-85
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

• To report information about one or more timing arcs, use the report_lib_timing_arcs
command. You must use the -objects option to specify the library timing arcs.
The easiest way to specify the timing arcs is to use the get_lib_timing_arcs
command and use the -of_objects option to specify the library cell for which you want
to report the timing arcs.
By default, the report includes the from pin, to pin, sense, when condition, and SDF
condition for the specified timing arcs.
For example, to report on all the timing arcs of the AND4 cell in the myreflib reference
library, use the following command:
icc2_lm_shell> report_lib_timing_arcs \
-objects [get_lib_timing_arcs -of_objects myreflib/AND2]
****************************************
Report : lib_timing_arc
****************************************

from to sense when sdf_cond is_disabled

------ ------ --------------- ---------- --------------- -----------
A1 Y positive_unate false
A2 Y positive_unate false
A1 Y positive_unate false
A2 Y positive_unate false
1

You can customize the report by using the -columns option to specify the information to
report. The following column names are valid for this report: from, from_lib_pin,
is_disabled, is_user_disabled, sdf_cond, sense, to, to_lib_pin, and when. To
display all of the available information, specify -columns all.

Exporting Reference Library Content

You can export reference library content to several formats for use with other tools. Table 2-9
lists the supported formats and the command used to generate the output files.
Table 2-9 Reference Library Export Formats

Format Command

Technology file write_tech_file

Antenna properties in Cell write_clf_antenna_properties

Library Format (CLF)

LEF write_lef

Chapter 2: Preparing Reference Libraries

Exporting Reference Library Content 2-86
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table 2-9 Reference Library Export Formats (Continued)

Format Command

GDSII write_gds

OASIS write_oasis

Design Compiler Graphical export_dc_fram

reference library

Closing a Reference Library

To close a reference library that was opened outside of a library workspace, use the
close_lib command. This command decrements the open count of the library and
removes it from memory when no copies of the library remain open.
Note:
To remove a reference library from a library workspace, use the remove_lib command.
By default, the close_lib command closes the current library. To close a specific library,
specify the library name. To close all libraries, use the -all option.
For example, to close the current library, use the following command:
icc2_lm_shell> close_lib

To close the myreflib.ndm reference library, use the following command:

icc2_lm_shell> close_lib myreflib.ndm

To close all reference libraries, use the following command:

icc2_lm_shell> close_lib -all

Chapter 2: Preparing Reference Libraries

Closing a Reference Library 2-87
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Chapter 2: Preparing Reference Libraries

Closing a Reference Library 2-88
A
Library Manager Application Options A
To learn about the application options you can use to control the behavior of the IC Compiler
II library manager, see the following topics:
• Library Manager Application Options
• LEF Input Application Options
• GDSII and OASIS Input Application Options
• Timing View Generation Application Options
• Frame View Generation Application Options
• Antenna Extraction Application Options
• Command-Line Interface Application Options
• Graphical User Interface Application Options

A-1
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Library Manager Application Options

The library manager (lib.workspace) application options control various aspects of the
reference library creation process. Table A-1 describes the lib.workspace application
options. If the application option has a data type of Boolean or enumerated string, the valid
values are listed, with the default listed first and shown in purple; otherwise, the data type is
specified along with the default.
Table A-1 lib.workspace Application Options

Application option Valid values or data type Description

lib.workspace.allow_commit_ false | true Controls whether the

workspace_overwrite commit_workspace command
overwrites an existing reference
library (true) or issues an error
message if the library already exists
(false).

lib.workspace.allow_missing_related_ false | true Controls whether the

pg_pins check_workspace command
requires signal pins to have at least
one related power or ground pin.

lib.workspace.create_workspace_tf_ true | false When true, the create_workspace

verbose -technology command outputs
detailed information when reading
the technology file.

lib.workspace.enable_secondary_ true | false Controls whether secondary power

pg_marking and ground pins are annotated on
the frame view.

lib.workspace.exclude_design_filters list Specifies one or more patterns to

(default = ””) match designs to exclude when
loading logic or physical libraries.
This option works with the
lib.workspace.include_design_
filters application option to
determine the set of designs to read.
For more information, see
Specifying Which Blocks to Process.

Appendix A: Library Manager Application Options

Library Manager Application Options A-2
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-1 lib.workspace Application Options (Continued)

Application option Valid values or data type Description

lib.workspace.explore_create_ false | true Controls the behavior of the

aggregate write_workspace and
commit_workspace commands
when the exploration flow creates
multiple workspaces.
To create an aggregate library, set
this application option to true.

lib.workspace.fast_exploration false | true Controls whether the fast

exploration flow is enabled.
For more information, see Using the
Exploration Flow.

lib.workspace.group_libs_create_slg false | true Controls whether the group_libs

command creates scaling groups.
For more information, see
Performing Automated Library
Analysis.

lib.workspace.group_libs_fix_cell_ true | false Controls whether the group_libs

shadowing command modifies the grouping
strategy to prevent cell shadowing
issues across subworkspaces.
Cell shadowing occurs when a
library cell with the same name
exists in multiple reference libraries.
In this case, the tool uses the data
from the first reference library in
which it finds the cell, and it ignores
that cell’s data in all other reference
libraries, which can result in missing
data for the cell.

lib.workspace.group_libs_macro_ aggregate_single_cell | Controls the macro grouping

grouping_strategy single_cell_per_lib strategy used for the
subworkspaces created by the
group_libs command.
For more information, see
Performing Automated Library
Analysis.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Library Manager Application Options A-3
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Table A-1 lib.workspace Application Options (Continued)

Application option Valid values or data type Description

lib.workspace.group_libs_naming_ list Controls the naming strategy used

strategies (default = ””) for the subworkspaces created by
the group_libs command.
By default, the tool creates the
subworkspace names by using a
unique combination of logic library
prefix and suffix characters.
For more information, see
Performing Automated Library
Analysis.

lib.workspace.group_libs_physical_ string Specifies the name of the

only_name (default = ””) physical-only library group created
by the group_libs command.
If this application option has a value
of “”, the command names the
physical-only subworkspace
<root_workspace>_physical_only.
For more information, see
Performing Automated Library
Analysis.

lib.workspace.include_design_filters list Specifies one or more patterns to

(default = ””) match designs to include when
loading logic or physical libraries.
When you set this option, only the
specified designs are read.
This option works with the
lib.workspace.exclude_design_
filters application option to
determine the set of designs to read.
For more information, see
Specifying Which Blocks to Process.

lib.workspace.remove_frame_bus_ false | true Controls whether the

properties check_workspace command
removes bus properties that exist in
the frame view but not in the timing
view.

Appendix A: Library Manager Application Options

Library Manager Application Options A-4
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-1 lib.workspace Application Options (Continued)

Application option Valid values or data type Description

lib.workspace.save_design_views false | true Controls whether the

commit_workspace command
saves the design views in the
reference library.

lib.workspace.save_layout_views false | true Controls whether the

commit_workspace command
saves the layout views in the
reference library.

LEF Input Application Options

The LEF input (file.lef) application options control the behavior of the read_lef
command. Table A-2 describes the file.lef application options. If the application option
has a data type of Boolean or enumerated string, the valid values are listed, with the default
shown in purple; otherwise, the data type is specified along with the default.
Table A-2 file.lef Application Options

Application option Valid values or Description

data type

file.lef.allow_empty_pin false | true Controls whether the read_lef

command allows a PIN statement
that does not have an associated
PORT.

file.lef.auto_rename_conflict_sites false | true Controls whether the read_lef

command automatically renames
conflicting site names.
For more information about this
application option, see Reading
LEF Files.

file.lef.non_real_cut_obs_mode true | false Controls whether to use zero

minimum spacing for non-real cut
obstructions.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
LEF Input Application Options A-5
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

GDSII and OASIS Input Application Options

The read_gds and read_oasis commands support similar application options to control
their behavior. Table A-3 describes these application options; replace format in the
application option names with gds for the read_gds command and oasis for the
read_oasis command. These application options also affect the trace_connectivity
commands.
In the following table, if the application option has a data type of Boolean or enumerated
string, the valid values are listed, with the default shown in purple; otherwise, the data type
is specified along with the default.
Table A-3 file.gds Application Options

Application option Valid values or Description

data type

file.format.create_custom_via false | true Controls whether the commands

create custom vias from the cut
shapes in the library source file.

file.format.exclude_layers list Specifies the rules for mapping

(default = “”) between the input layers and the
layers that are used to exclude
geometries from the specified input
layers.

file.format.port_type_map list Identifies the power and ground

(default = “”) pins by mapping the pin name to its
type. The mapping applies to all
cells in the library source file.
For more information about this
application option, see Reading
GDSII or OASIS Files.

Appendix A: Library Manager Application Options

GDSII and OASIS Input Application Options A-6
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-3 file.gds Application Options (Continued)

Application option Valid values or Description

data type

file.format.text_layer_map list Maps the text layers to the metal

(default = “”) layers so that the tool can
associate metal shapes with a net
or pin when the text is not on the
same layer as the metal shapes.
For more information about this
application option, see Mapping
Text Layers.

file.format.trace_copy_overlap_ false | true Controls whether the commands

shape_from_sub_cell duplicate a shape in a subblock to
the top-level block when the shape
is overlapped by terminals.

file.format.trace_unmapped_text false | true Controls whether the commands

trace all routing layers for text that
is not mapped to any routing layer.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
GDSII and OASIS Input Application Options A-7
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Timing View Generation Application Options

The timing view generation (lib.logic_model) application options control the timing view
generation, which is performed by the check_workspace command. Table A-4 describes
the lib.logic_model application options. If the application option has a data type of
Boolean or enumerated string, the valid values are listed, with the default shown in purple;
otherwise, the data type is specified along with the default.
Table A-4 lib.logic_model Application Options

Application option Valid values or Description

data type

lib.logic_model.auto_remove_ false | true Controls whether the

incompatible_timing_designs check_workspace command
automatically removes cells from the
reference library that have a
mismatch between the base library
and additional logic libraries.

lib.logic_model.auto_remove_ false | true Controls whether the

timing_only_designs check_workspace command
automatically removes cells from the
reference library that do not exist in
the physical library.

lib.logic_model.relax_pin_equal_ false | true Controls whether the

opposite_attr_check check_workspace command
requires that the pin_equal and
pin_opposite attributes on a cell
must match between the base
library and additional logic libraries.

lib.logic_model.resolve_voltage_ use_base_library Specifies how to handle voltage

range_differences | require_same range differences across the logic
libraries.

Appendix A: Library Manager Application Options

Timing View Generation Application Options A-8
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-4 lib.logic_model Application Options (Continued)

Application option Valid values or Description

data type

lib.logic_model.require_same_ false | true Controls whether the

opt_attrs check_workspace command
requires that the optimization
attributes on a cell must match
between the base library and
additional logic libraries.

lib.logic_model.use_db_rail_names true | false When true, the commit_workspace

command uses the voltage rail
names from the logic libraries;
otherwise, it generates the names.

Frame View Generation Application Options

The frame view generation (lib.physical_model) application options control the frame
view generation, which is performed by the check_workspace command. Table A-5
describes the lib.physical_model application options. If the application option has a data
type of Boolean or enumerated string, the valid values are listed, with the default shown in
purple; otherwise, the data type is specified along with the default.
Table A-5 lib.physical_model Application Options

Application option Valid values or data Description

type

lib.physical_model.block_all auto | false | Controls whether the entire cell,

true | used_layers except for the area around the pins,
| top_layer
is treated as a blockage in the frame
view.
If you specify the top_layer
argument, the tool creates a
zero-spacing blockage on the
specified layer and all layers below it;
otherwise, the setting applies to all
layers.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Frame View Generation Application Options A-9
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Table A-5 lib.physical_model Application Options (Continued)

Application option Valid values or data Description

type

lib.physical_model.block_core_ list of layer-float pairs Specifies the margin between the

margin (default = “”) core blockage and the macro cell
boundary for each layer in the frame
view.
If you specify this option for a layer,
the tool creates a core blockage with
the specified margin regardless of
the setting of the
lib.physical_model.block_all
application option.

lib.physical_model.color_based_ auto | true | Controls whether frame generation

dpt_flow false uses the color-based flow.
By default (auto), frame generation
uses the color-based flow when the
technology file contains
double-patterning rules.

lib.physical_model.connect_ true | false Controls whether the via enclosure

within_pin must be within the pin shape. when
dropping a via on the via region.

lib.physical_model.convert_ list of Converts metal blockages in the

metal_blockage_to_zero_spacing layer-distance-mode design views to zero-spacing routing
triplets blockages in the frame views for the
(default = “”) specified layers. When creating the
zero-spacing routing blockage, the
tool increases the size of the metal
blockage by the distance specified
for that layer.
By default, the specified distance
applies to all metal blockages. To
specify different distances based on
whether the blockage touches a pin,
specify the optional mode argument
as either touch_pin or
no_touch_pin.

Appendix A: Library Manager Application Options

Frame View Generation Application Options A-10
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-5 lib.physical_model Application Options (Continued)

Application option Valid values or data Description

type

lib.physical_model.create_frame_ false | true Controls whether frame view

for_subblocks generation creates a frame view only
for the top-level block (the default) or
for the top-level block and the
subblocks.

lib.physical_model.create_zero_ list of layer-width Specifies the width of the

spacing_blockages_around_pins pairs zero-spacing routing blockages
(default = “”) created around the pins for each
layer in the frame view.
By default, frame view generation
does not create zero-spacing routing
blockages around the pins.

lib.physical_model.design_rule_ list of via layers Converts zero-spacing routing

via_blockage_layers (default = “”) blockages on the via layers of the
frame view to design rule routing
blockages.

lib.physical_model.drc_distances list of layer-distance Specifies the distance from the

pairs boundary of blockages within with to
(default = “”) preserve detail shapes.
By default, the tool uses information
in the Layer section of the technology
file to determine this value for each
layer. The value is computed by
adding the maximum spacing value
to the maximum width threshold from
the fat spacing table.

lib.physical_model.hierarchical true | false Controls whether the tool extracts

pins, vias, and blockages
hierarchically when creating the
frame view.

lib.physical_model.include_ list Specifies the nondefault vias to

nondefault_via (default = “”) include for via region extraction.

lib.physical_model.include_ list Specifies the PG ports that requires

routing_pg_ports (default = “”) via regions and access edges in the
frame views.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Frame View Generation Application Options A-11
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Table A-5 lib.physical_model Application Options (Continued)

Application option Valid values or data Description

type

lib.physical_model.keepout_ list of layer-spacings Defines how to create the

spacing_for_non_pin_shapes pairs zero-spacing routing blockages for
(default = “”) the non-pin shapes on each affected
layer.

lib.physical_model.merge_ false | true Controls whether metal blockages

metal_blockage are merged if they are too close,
based on the minimum width and
minimum spacing for the layer.

lib.physical_model.pin_channel_ list of layer-distance Controls the channel distance for

distances pairs each pin layer. If a pin is within the
(default = “”) channel distance of the block
boundary, the tool cuts a channel for
the pin when generating the frame
view.

lib.physical_model.pin_must_ list of layer-spare Specifies the spare layer associated

connect_area_layers layer pairs with each pin layer. The spare layer
(default = “”) defines the must-area within the pin
geometry.
Use this option to restrict the via
landing area on complex-shaped
pins.

lib.physical_model.pin_must_ list of layer-threshold Specifies the width threshold used to

connect_area_thresholds pairs determine the must-connect area
(default = “”) within the pin geometry for each
connection layer.
Use this option to restrict the via
landing area on finger-shaped pins.

lib.physical_model.port_contact_ string Specifies custom contact codes for

selections (default = “”) specific ports for via region
generation.

Appendix A: Library Manager Application Options

Frame View Generation Application Options A-12
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-5 lib.physical_model Application Options (Continued)

Application option Valid values or data Description

type

lib.physical_model.preserve_ auto | true | Controls whether metal blockages

metal_blockage false are trimmed when creating the frame
view.
By default, metal blockages are
preserved (not trimmed) for the
following types of cells: library cells,
diode cells, end cap cells, fill cells,
filler cells, physical-only cells, and
well-tap cells.
For all other types of cells, the tool
trims metal blockages that touch a
pin.

lib.physical_model.remove_ list of layer-mode Specifies whether to remove non-pin

non_pin_shapes pairs shapes when generating the frame
(default = “”) view. Valid values for the mode are
• none (the default)
Frame generation does not
remove non-pin shapes.
• all
Frame generation removes all
non-pin shapes on the specified
layer.
• core
Frame generation removes all
non-pin shapes that are
completely within the core on the
specified layer. The core is
determined by shrinking the block
boundary by the DRC distance.
Removing non-pin shapes reduces
the number of blockages in the frame
view. However, to ensure that the
removal of the non-pin shapes from
the frame view does not cause
routing DRC violations, you should
create a core blockage by using the
lib.physical_model.block_all or
lib.physical_model.block_
core_margin application option.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Frame View Generation Application Options A-13
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Table A-5 lib.physical_model Application Options (Continued)

Application option Valid values or data Description

type

lib.physical_model.source_drain_ string Specifies the name of the input file

annotation (default = “”) containing the source-drain
annotation information for the cells in
the library workspace.

lib.physical_model.trim_metal_ list of layer-method Specifies how to trim metal

blockage_around_pin pairs blockages around pins for each layer.
(default = “”) Valid values for the method are
touch, all, and none.
If you specify this option for a layer,
the tool uses the specified method to
trim the metal blockages for that layer
regardless of the setting of the
lib.physical_model.
preserve_metal_blockage
application option.

Appendix A: Library Manager Application Options

Frame View Generation Application Options A-14
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Antenna Extraction Application Options

The antenna extraction (signoff.antenna) application options control the IC Validator
antenna extraction that occurs during frame view generation by the check_workspace
command. Table A-6 describes the signoff.antenna application options. If the application
option has a data type of Boolean or enumerated string, the valid values are listed, with the
default shown in purple; otherwise, the data type is specified along with the default.
Table A-6 signoff.antenna Application Options

Application option Valid values or Description

data type

signoff.antenna.contact_layer list Specifies the contact layers

(default = “”) (contact layers are the layers that
connect polysilicon to metal1).
Specify the layers by using the
layer names from the technology
file.

signoff.antenna.contact_layers_ list Specifies the contact layers

between_m0_diffusion (default = “”) (contact layers are the layers that
connect metal0 to diffusion).
Specify the layers by using the
layer names from the technology
file.

signoff.antenna.diffusion_layer list Specifies the diffusion layers.

(default = “”) Specify the layers by using the
layer names from the technology
file.

signoff.antenna.enabled false | true Controls whether the

check_workspace command
performs antenna extraction during
frame view generation.

signoff.antenna.extract_via_antenna false | true Controls whether antenna

_property properties are extracted for via
layers.

signoff.antenna.gate_class1_layers list Specifies the marking layers for

(default = “”) gate thickness class 1. Specify the
layers by using the layer names
from the technology file.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Antenna Extraction Application Options A-15
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Table A-6 signoff.antenna Application Options (Continued)

Application option Valid values or Description

data type

signoff.antenna.gate_class2_layers list Specifies the marking layers for

(default = “”) gate thickness class 2. Specify the
layers by using the layer names
from the technology file.

signoff.antenna.gate_class3_layers list Specifies the marking layers for

(default = “”) gate thickness class 3. Specify the
layers by using the layer names
from the technology file.

signoff.antenna.m0_layers_for_ string Specifies the m0 layers for

diffusion_connection (default = “”) diffusion connection. Specify the
layers by using the layer names
from the technology file.

signoff.antenna.m0_layers_for_ string Specifies the m0 layers for poly

poly_connection (default = “”) connection. Specify the layers by
using the layer names from the
technology file.

signoff.antenna.poly_layer list Specifies the polysilicon layers.

(default = “”) Specify the layers by using the
layer names from the technology
file.

signoff.antenna.report_diodes false | true Controls whether the tool reports

the location of generated
protection diodes.

signoff.antenna.top_cell_pin_only false | true Controls whether the tool extracts

hierarchical antenna properties
only for nets that connect to pins in
the top-level of the hard macro.

signoff.antenna.treat_source_ false | true Controls whether the tool treats the

drain_as_diodes MOS source and drain as
protection diodes and considers
any MOS source and drain regions
that are connected to a net to be a
part of the diode protection area
available to that net.

Appendix A: Library Manager Application Options

Antenna Extraction Application Options A-16
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Table A-6 signoff.antenna Application Options (Continued)

Application option Valid values or Description

data type

signoff.antenna.user_defined_ list Specifies additional options for the

options (default = “”) IC Validator command line.
The string that you specify in this
option is added to the command
line used to invoke antenna
extraction in the IC Validator tool.
The library manager does not
perform any checking on the
specified string.

signoff.antenna.v0_layers_ list Specifies the v0 layers (v0 layers

between_m1_m0 (default = “”) are the layers that connect metal1
to metal0). Specify the layers by
using the layer names from the
technology file.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Antenna Extraction Application Options A-17
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Command-Line Interface Application Options

The shell application options control various aspects of the library manager command-line
interface. Table A-7 describes the shell application options. If the application option has a
data type of Boolean or enumerated string, the valid values are listed, with the default shown
in purple; otherwise, the data type is specified along with the default.
Table A-7 shell Application Options

Application option Valid values or Description

data type

shell.common.collection_result_ integer Specifies the maximum number of results

display_limit (default = 100) displayed when the return value is a
collection.

shell.common.enable_line_editing true | false Controls whether line editing mode is

enabled.

shell.common.line_editing_mode emacs | vi Specifies the line editing mode.

shell.common.man_path string Specifies the search path for the man

pages.

shell.common.report_default_ integer Specifies the default number of significant

significant_digits default = 2) digits used to display values in reports.

shell.common.single_line_messages false | true When set to true, error, warning, and

information messages that contain
newlines are output without newlines.

shell.common.tmp_dir_path string Specifies the directory that the tool uses

(default = /tmp) for temporary storage.

Appendix A: Library Manager Application Options

Command-Line Interface Application Options A-18
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Graphical User Interface Application Options

The gui application options control various aspects of the library manager GUI. Table A-8
describes the gui application options. If the application option has a data type of Boolean or
enumerated string, the valid values are listed, with the default shown in purple; otherwise,
the data type is specified along with the default.
Table A-8 gui Application Options

Application option Valid values or Description

data type

gui.auto_link_blocks true | false Controls whether the tool automatically

links the current block.

gui.auto_open_layout_windows true | false Controls whether the GUI automatically

creates a block window when the current
design changes.

gui.command_form_close_dialog_ false | true Controls whether a shell command form

after_run_or_script invoked from a command search closes
itself after the command is successfully
executed or scripted.

gui.command_form_show_result_ false | true Controls whether a shell command form

dialog_after_run invoked from a command search displays
the results from the command execution in
a dialog box.

gui.custom_setup_files string Specifies the files to source when invoking

(default = “”) the GUI. These files are sourced in
addition to the standard setup files.

gui.enable_custom_setup_files false | true Controls whether the tool sources the

custom setup files specified in the
gui.custom_setup_files application
option.

gui.layer_solid_fill_pattern string Controls default display of solid filled

(default = layers.
Dense4Pattern) To see the valid values for this application
option, use the get_app_option_value
-details -name
gui.layer_solid_fill_pattern
command.

AppendixA:A:Library
Chapter LibraryManager
ManagerApplication
ApplicationOptions
Options
Graphical User Interface Application Options A-19
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Appendix A: Library Manager Application Options

Graphical User Interface Application Options A-20
B
Working With the Library Manager GUI B
The library manager GUI provides a variety of tools for viewing and editing the cells in your
library. The following topics provide an overview of these tools:
• Starting the Tool in the GUI
• Opening the GUI
• Closing the GUI
• Exiting the Tool From the GUI
• Using the Library Preparation Wizard
• Working in the Main Window
• Using the Message Browser Window

B-1
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Starting the Tool in the GUI

To start the IC Compiler II Library Manager tool in the GUI,
1. Set the DISPLAY environment variable to the name of your UNIX or Linux system
display.
2. Include the path to the bin directory in your $PATH variable.
3. Enter the icc2_lm_shell command with the -gui option in a UNIX or Linux shell.
% icc2_lm_shell -gui

You can include other options when you start the GUI. For example,
❍ -f script_file_name to execute a script

❍ -x command to execute an icc2_lm_shell command

When you start the library manager in the GUI, it

1. Runs the commands in the .synopsys_icc2_lm.setup and .synopsys_icc2_lm_gui/
setup.tcl setup files
The tool first runs the setup files in your home directory followed by the files in the project
directory (the current working directory in which you start the tool).
2. Runs the command specified by the -x option or the script specified by the -f option.
3. Opens a main window that displays the library preparation wizard
By default, the console appears attached (docked) to the main window above the status
bar.

See Also
• Starting the Command-Line Interface

Appendix B: Working With the Library Manager GUI

Starting the Tool in the GUI B-2
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Opening the GUI

If you start icc2_lm_shell without the GUI, you can open the GUI at any time by entering the
gui_start command at the icc2_lm_shell> prompt.
icc2_lm_shell> gui_start

If you want to execute a script before opening the GUI, use the -file option. For example,
icc2_lm_shell> gui_start -file my_gui_setup.tcl

Note:
The GUI uses the DISPLAY environment variable to determine the display location.
Before opening the GUI, ensure that this variable is set to the name of your UNIX or
Linux system display.
When you open the library manager GUI, it
1. Runs the commands in the .synopsys_icc2_lm_gui/setup.tcl setup files
The tool first runs the setup files in your home directory followed by the files in the project
directory (the current working directory in which you start the tool).
2. Runs the script specified by the -file option.
3. Opens a main window
❍ If a library workspace or reference library is open, it opens the library browser in the
main window.
The library browser is a hierarchical representation of the library workspace or
reference library.
❍ if a library workspace or reference library is not open, it opens the library preparation
wizard in the main window.

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Opening the GUI B-3
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Closing the GUI

You can open or close the GUI at any time during the session. For example, if you need to
conserve system resources, you can close the GUI and continue the session in
icc2_lm_shell.
To close the GUI, do one of the following:
• Choose File > Close GUI in the block window.
• Choose Window > Close All Windows (Close GUI) in any GUI window.
• Enter the gui_stop command.
icc2_lm_shell> gui_stop

Exiting the Tool From the GUI

To exit the library manager from the GUI, enter the exit or quit command or choose File
> Exit.
Note:
The library manager does not save the view settings when you exit. For information
about saving changed view settings, see the IC Compiler II Graphical User Interface
User Guide.

See Also
• Exiting the IC Compiler II Library Manager Tool

Appendix B: Working With the Library Manager GUI

Closing the GUI B-4
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Using the Library Preparation Wizard

The library preparation wizard is an easy-to-use tool for navigating the library preparation
flow and executing the individual tasks to create and modify your reference libraries.
Figure B-1 shows the start page of the library preparation wizard.
Figure B-1 Library Preparation Wizard

The following topics describe how to use the wizard to perform these tasks:
• Creating a Reference Library
• Modifying a Reference Library
• Viewing a Reference Library

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Using the Library Preparation Wizard B-5
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Creating a Reference Library

To use the library preparation wizard to create a new reference library,

1. Click the create icon ( ) or the “Create a new library” link.

The “Set up ‘Exploration’ Workspace” dialog box (Figure B-2) appears.
Figure B-2 Set up “Exploration” Workspace Dialog Box

2. Select the library preparation flow in the Flow text box.

By default, the exploration flow is selected. To use another flow, select the flow from the
drop-down list.
3. Specify the workspace name in the Workspace text box.
4. Specify the technology data source.
You can specify either a technology file, which must have a file extension of .tf, or a
technology library, which must have a file extension of .ndm. You can either enter the file
path or click to browse for it.

Appendix B: Working With the Library Manager GUI

Using the Library Preparation Wizard B-6
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

5. Read the library source files.

To read the source files,
a. Click the tab associated with the file type (DB for the logic libraries; LEF, GDS, or
NDM for the physical libraries) and click Add, which opens the Open dialog box.
b. Browse to the directory that contains the library source files, select the files, and click
Open. To select multiple files, hold the Ctrl key.
When you open library source files, they appear in the “Set up ‘Exploration’
Workspace” dialog box.
c. Click Read to read the source files listed in the dialog box.
For details about reading library source files, see Loading the Logic Libraries and
Loading the Physical Libraries.
6. Click OK to finish the workspace setup.
The library browser is updated to display the libraries loaded into the library workspace,
as shown in Figure B-3.
Figure B-3 Library Browser After Loading Source Libraries

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Using the Library Preparation Wizard B-7
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

7. Configure the PVT filtering.

The library manager displays the current PVT configuration, as well as the filtering
statistics, as shown in Figure B-4.
Figure B-4 PVT Configuration

To modify the PVT configuration,

a. Select Configure.
The Filter Process/Voltage/Temperature dialog box appears. The dialog box displays
the settings available in the logic libraries loaded in step 5.
b. Select the process, voltage, and temperature settings and click OK.
By default, the filtered logic libraries are not shown in the library browser. To display
the filtered logic libraries, select “Show filtered files.” When you select this option, the
library browser displays the filtered files in gray italic text.
For details about configuring PVT filtering, see Filtering Logic Libraries Based on
Operating Corners.
8. Create the subworkspaces by selecting Group Libs and then clicking OK in the Group
Libraries dialog box.
The library browser is updated to display the library groups created by the library
preparation wizard, as shown in Figure B-5.
Figure B-5 Library Browser After Grouping Libraries

Appendix B: Working With the Library Manager GUI

Using the Library Preparation Wizard B-8
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

9. Validate the workspace by selecting Check Workspace and then clicking OK in the
Check Workspace dialog box.
The workspace must pass validation before you can create a reference library. For
details about workspace validation, see Validating the Workspace.
10.Create the reference library by selecting Commit Workspace and then clicking OK in the
Commit Workspace dialog box.

Modifying a Reference Library

To use the library preparation wizard to modify an existing reference library,

1. Click the edit icon ( ) or the “Edit a library” link.

The “Set up ‘Edit’ Workspace” dialog box (Figure B-6) appears.
Figure B-6 Set up “Edit” Workspace Dialog Box

2. Specify the library in the Library text box.

You can either enter the file path or click to browse for it.

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Using the Library Preparation Wizard B-9
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

3. If you want to update the technology data for the reference library, specify the technology
data source in the Technology text box.
You can specify either a technology file, which must have a file extension of .tf, or a
technology library, which must have a file extension of .ndm. You can either enter the file
path or click to browse for it.

4. Read the physical library source files.

To read the physical library source files,
a. Click the tab associated with the file type you want to read (LEF, GDS, or NDM) and
click Add, which opens the Open dialog box.
b. Browse to the directory that contains the library source files, select the files, and click
Open. To select multiple files, hold the Ctrl key.
When you open library source files, they appear in the “Set up ‘Edit’ Workspace”
dialog box.
c. Click Read to read the source files listed in the dialog box.
For details about reading physical library source files into an edit workspace, see
Modifying a Reference Library.
5. Validate the workspace by selecting Check Workspace in the library browser and then
clicking OK in the Check Workspace dialog box.
The workspace must pass validation before you can create a reference library. For
details about workspace validation, see Validating the Workspace.
6. Save the updated reference library by selecting Commit Workspace and then clicking
OK in the Commit Workspace dialog box.

Appendix B: Working With the Library Manager GUI

Using the Library Preparation Wizard B-10
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Viewing a Reference Library

You can use the GUI to list the cells in a reference library, view information about the cells,
and view the layout of the cells.
To use the library preparation wizard to view an existing reference library,

1. Click the folder icon ( ) or the “View an existing library” link.

The Open Library dialog box appears.
2. Select the reference library.
You can either enter the path to the reference library or click to browse for it.

3. If you want to edit the reference library, select “Open reference library for edit.”
4. Click OK.
The library browser opens with the selected reference library.

See Also
• Using the Library Browser

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Using the Library Preparation Wizard B-11
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Working in the Main Window

When you start the library manager tool and open the GUI, the main window appears.
Figure B-7 identifies the major features of the main window.
Figure B-7 Main Window Features

Menus

Library
browser

Console

Command line
(part of console)

Status bar

Typically, you use the main window to

• Run Tcl scripts
• Enter icc2_lm_shell commands, monitor command processing, and view messages in
the console
• Open and close libraries and blocks (library cells or designs)
• Explore reference libraries in the library browser
• Set application options

Appendix B: Working With the Library Manager GUI

Working in the Main Window B-12
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

• Open other GUI windows

• Close the GUI or exit the tool

Using the Library Browser

You can use the library browser to view the cells in the source logic and physical libraries in
a library workspace or the cells in a reference library.
The library browser shows a hierarchical view of the libraries loaded in memory. If a library
workspace is open, it shows its source libraries; otherwise, it shows the open reference
libraries. You can expand each library to show the blocks (library cells or designs) in the
library. You can expand each block to show the views available for the block. The library
browser also reports the number and types of cell views in the library. Figure B-8 shows a
library browser that displays an expanded reference library with one of its cells expanded to
show its views.
Figure B-8 Library Browser

To sort the blocks displayed in the library browser, click the caret (^) in the browser header.
To filter the blocks, enter a string in the search box. As you type, the library browser updates
to show only blocks that contain the text you entered. Click the X to the right side of the text
box to clear the filter.

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Working in the Main Window B-13
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

To open a block in a block window to view or modify its layout, select a physical view (frame,
design, or layout) of the block, right-click, and choose Open Layout View. For information
about using the block window, see the IC Compiler II Graphical User Interface User Guide.
To see detailed information about the library cells, display the library browser cell
information.
• To display information for a specific cell, select one of its views and choose Cell
Information from the context-sensitive menu.
• To display information for all cells in the library, click the “Cell info” button, which is
located at the bottom right of the library browser.

Figure B-9 shows these features in the library browser. Figure B-10 shows an example cell
information report.
Figure B-9 Displaying Cell Information in the Library Browser

Figure B-10 Cell Information Report

Appendix B: Working With the Library Manager GUI

Working in the Main Window B-14
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

Using the Message Browser Window

After you run the check_workspace command, you can view the messages in the message
browser. To view the messages, load the message database by choosing File > Open
Message Database, and then select the check_workspace.ems file. The message browser
lists each of the messages (information, warning, and error) that was issued by the
check_workspace command, as well as the message status (W:waived, F:fixed, and
A:active). To display the man page for a message, select the message in the browser view.
Figure B-11 shows an example of a message browser window.
Figure B-11 Message Browser

See Also
• “Using the Message Browser” topic in the IC Compiler II Graphical User Interface User
Guide

AppendixB:B:Working
Chapter WorkingWith
Withthe
theLibrary
LibraryManager
ManagerGUI
GUI
Using the Message Browser Window B-15
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Appendix B: Working With the Library Manager GUI

Using the Message Browser Window B-16
C
Using Non-PG Logic Libraries C
This topic describes the following workspace checks when using logic libraries that do not
use the PG-pin syntax:
• PG Rail Checks
• PG Pin Connections

C-1
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

PG Rail Checks
For logic libraries that do not use the PG-pin syntax, the power rails and pins are derived
from the library-level power_supply group and cell-level rail_connection attributes. The
power_rail attributes in the power_supply group define the power rail names. The
rail_connection attributes on a cell associate these power rails with the cell’s power pins.
The signal pins of a cell are associated with the PG rails by using the pin-level
input_signal_level and output_signal_level attributes. Example C-1 shows the use
of these attributes to define the power connections in a .lib logic library file.
Example C-1 Library Example With power_supply Group
library (my_lib) {
...
power_supply () {
default_power_rail : VDD085;
power_rail (VDD085, 0.85);
power_rail (VDD105, 1.05);
power_rail (VDD120, 1.20);
}
...
cell (LS_085_105) {
is_level_shifter : true;
rail_connection (VDDH, VDD105) ;
rail_connection (VDDL, VDD085) ;
...
pin (in) {
direction : input;
input_signal_level : VDDL;
...
}
pin (out) {
direction : output;
output_signal_level : VDDH;
...
}
...
} /* end cell group*/
...
} /* end library group*/

The tool verifies that each logic library has the same number of rails and they have the same
names; however, if a rail is defined in a power_supply group but is not used, the tool ignores
mismatches involving that rail and does not include the rail definition in the generated
reference library.
If the rail order differs, the tool automatically updates the order using the information from
the base library.

Appendix C: Using Non-PG Logic Libraries

PG Rail Checks C-2
IC Compiler™ II Library Preparation User Guide Version M-2016.12-SP4

By default, if a rail name differs between the logic libraries, the tool issues an LM-043 error.
If the mismatch is caused only by rail names and positions, and not rail type differences, you
can use the rename_rail command to make the rail names match. For example, assume
logic library A has a power_rail setting of (VDD1.0, 1.0) and logic library B has a
power_rail setting of (VDD1.1, 1.1). You could use the rename_rail command to align
these rails, as shown in the following example:
icc2_lm_shell> rename_rail -library A -from VDD1.0 -to VDD
icc2_lm_shell> rename_rail -library B -from VDD1.1 -to VDD

You can also use the rename_rail command to correct the situation where the
rail_connection attribute for a cell uses the same PG pin name across libraries, but the
rail name differs.

PG Pin Connections
If the rail name specified for a rail_connection attribute is not defined in the library-level
power_supply group, the tool issues an error message. To fix this error, use the
set_attribute command to change the rail_connection attribute to a valid rail name.
To see the rail names defined for a library workspace, use the report_workspace -panes
command.

AppendixC:C:Using
Chapter UsingNon-PG
Non-PGLogic
LogicLibraries
Libraries
PG Pin Connections C-3
IC Compiler™ II
IC Compiler™ II Library
Library Preparation
Preparation User
User Guide
Guide Version M-2016.12-SP4
M-2016.12-SP4

Appendix C: Using Non-PG Logic Libraries

PG Pin Connections C-4