Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Is there a way to release the memory used by the makeTable() function? If you assign nil to the variable holding the table object, will the table be deleted and the memory freed?
I would like to use makeTable in a pcell, however I'm worried about using too much memory if the table data is always around and duplicated wherever the pcell is used.
I could use remove(g_key o_table) on every element.
You may be aware that garbage collection is the process by which unused memory is reclaimed. There are various ways that memory can become unused, for example, it was allocated in a let statement and this block of code has been executed and exited, or as you state, by effectively removing references to the memory. Once all references to a chunk of memory have been removed, it is liable for garbage collection. This process occurs every so often, but can be initiated by the user also, using the gc() function. See the following section in the SKILL Language User Guide in SourceLink: "Memory Management (Garbage Collection)"
I would recommend using an encapsulation technique when writing your PCell code, so that the code that does all of the work is encapsulated in a procedure which can be debugged outside of the PCell development, and also potentially re-used by other PCells. Something like the following:
list( ddGetObj("libName") "cellName" "layout")
( paramA 1.0 )
( paramB 2.0 )
myPCellTopFunction( pcCellView paramA paramB )
Hopefully the above information and pointers will help you.
In reply to skillUser:
Also be aware that when you pass a table as an argument, you are passing a pointer to the table and not the values in it. So if you change a value in the table inside a program where it came in as an argument, you change the table itself.
HOWEVER- It is much faster and takes less memory to pass the table as an argument than to pass the very large list of individual arguments. If your table variable is defined in a let statement, it will be garbage collected when it finally goes out of scope.