Inheritance diagram for oaModVectorInstDef:
Public Methods | |
void | destroy () |
oaUInt4 | getMinIndex () const |
oaUInt4 | getMaxIndex () const |
oaUInt4 | getNumBits () const |
void | getName (oaScalarName &name) const |
void | getName (const oaNameSpace &ns, oaString &name) const |
oaBitOrder | getBitOrder () const |
oaBoolean | isImplicit () const |
void | setBitOrder (oaBitOrder order) |
oaCollection< oaModInst, oaModVectorInstDef > | getVectorInsts () const |
oaCollection< oaModInst, oaModVectorInstDef > | getVectorInstBits () const |
Static Public Methods | |
oaModVectorInstDef * | create (const oaModule *module, const oaScalarName &name, oaBitOrder order) |
oaModVectorInstDef * | find (const oaModule *module, const oaScalarName &name) |
Public Types | |
enum | { dtIndex = oacVectorInstDefDataType } |
A vectorInstDef can be 'sparse' (have missing bits). Vectors do not have to start or end at zero. For example, a[22:25]
is a legal vectorInst name. Vector indexes must be non-negative.
An vectorInstDef is automatically created if necessary whenever applications create vectorInsts. Implicitly created vectorInst definitions have no bitOrder. Applications may explicitly create a vectorInst definition in order to specify that it has a specific bitOrder.
The bit order of an explicit oaModVectorInstDef is independent of the order within individual oaModVectorInsts with the same base name. Verilog requires a single wire declaration for a given base name, and the range of that declaration covers all of the bit indices used by the sub-ranges that correspond to oaModVectorInsts.
Implicitly created vectorInst definitions are automatically destroyed when the last vectorInst with the same base name is destroyed. Explicitly created vectorInst definitions must be explicitly destroyed.
The oaModVectorInstDef class can be observed by deriving from oaObserver<oaModVectorInstDef>.
|
This function creates an oaModVectorInstDef in the specified module with the given base name and bit order. An exception is thrown if an oaModVectorInstDef already exists with the specified name. Explicitly creating an oaModVectorInstDef also means that the vectorInst definition must be explicitly destroyed.
|
|
This function destroys this oaModVectorInstDef, removing it from the database. An exception is thrown if the oaModVectorInstDef is implicit or if there are still oaModVectorInsts associated with it.
|
|
This function searches the specified module for a vectorInstDef with the specified name. The function returns the vectorInstDef if it finds it. Otherwise, NULL is returned. |
|
This function returns the bitOrder associated with this oaModVectorInstDef object. |
|
This function returns the largest bit number in use for this oaModVectorInstDef object. This is the largest index used across all vectorInsts associated with this oaModVectorInstDef object. |
|
This function returns the smallest bit number in use for this oaModVectorInstDef object. This is the smallest index used across all vectorInsts associated with this oaModVectorInstDef object. |
|
This function returns the name string of this oaModVectorInstDef object in the specified nameSpace.
|
|
This function returns the name of this oaModVectorInstDef object.
|
|
This function returns the number of bits covered by the vectorInsts in this oaModVectorInstDef. The number of bits is equal to abs(maxIndex - minIndex) + 1. |
|
This function returns a collection of oaModVectorInstBit and oaModModuleVectorInstBit objects associated with this oaModVectorInstDef object. |
|
This function returns a collection of oaModVectorInst and oaModModuleVectorInst objects associated with this oaModVectorInstDef object. |
|
This function returns a boolean indicating whether this oaModVectorInstDef was implicitly created or not. |
|
This function changes the bitOrder value associated with the oaModVectorInstDef. An exception is thrown if this vectorInstDef was implicitly created.
|
|
|
Copyright © 2002 - 2010 Cadence Design Systems, Inc.
All Rights Reserved.