• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. giolib045 "archaeology" (origin of giolib045.lib, giolib045...

Stats

  • Replies 0
  • Subscribers 126
  • Views 246
  • Members are here 0

giolib045 "archaeology" (origin of giolib045.lib, giolib045.gds files)

GS202507021424
GS202507021424 24 days ago

I am using gpdk045 (v6.0), gsclib045 (v4.7), and giolib045 (v3.3) with a new deployment of Cadence tools: IC231, SPECTRE, PEGASUS, QUANTUS, DDI (Innovus, Genus), etc.

I am trying to replicate the behavior of an existing, site-wide install that's been "evolving" over a number of years.

This exisging environment references two files: giolib045.lib (8.5K in size), and giolib045.gds (63M in size), and nobody can remember where they actually came from.

Notably, they are *NOT* part of the current giolib045 v3.3 tarball available for download from Cadence.

giolib045.lib contains the comment string "/* Models written by Liberate 12.1 from Cadence Design Systems, Inc. on Mon Apr 22 15:22:43 PDT 2013 */", similar to a lot of other *.lib files shipping as part of the gsclib045_all_v4.7 tar ball (e.g., gsclib045_all_v4.7/gsclib045_hvt/timing/*.lib). The gsclib045 distribution also ships a bunch of gds files.

I was wondering whether giolib045 did, at any point in the past, contain a (timing?) library and .gds file? The presence or absence of these files appears to make a difference in (hold) timing analysis as part of innovus signoff, particularly when density "pressure" is exerted via the `floorPlan` command...

This is mainly an exercies in giolib045 "archaeology" -- did it ship these files in the past, or did some long-retired engineer "extract" them from the giolib045 tarball-as-shipped, via some long-forgotten magic tool invocation? :)

Many thanks in advance!

  • Sign in to reply
  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information