[sv-cc] New erratas on Vpi

From: Francoise Martinolle <fm@cadence.com>
Date: Fri Apr 16 2004 - 13:18:47 PDT

Section 31.12 Typespec
Why do we have a var bit typespec , it does not make any sense.
This should be removed

the property vpiTagged should not be a string property but a boolean property

Note 3 and 17 should refer to section 31.22 instead of 31.21

There is an inconsistency between the description of the vpiArray property
in the notes and the fact that this property is labeled array member in the
diagram, I believe this is the result of the merg of the 1364 reg diagram
and 1364 variables diagram.
We have to choose a meaning for vpiArray for now the variables diagrams
which reprensent both regs and variables.

Additionally if you read notes 2 and 4, you would understand that a packed
array variable has the vpiArray True. Therefore the note 11 is wrong
because packed array variables have a value property. Only unpacked array
variables do not have the value property.

Note 19 is incorrect:

bit var bit = reg bit
it should be var bit= reg bit

In fact this is not a strict equivalence, we should rather say the the
vpiBitVar would be #defined the same as vpiRegBit for backward
compatibility, and you should note that a vpiVarBit could be a 2 state
scalar variable which is not a vpiRegBit since regs have 4 state values.

Note 20: we say that the vpiScalar property can be applied to a packed
struct or union, but does this mean that it will return true of the packed
union or struct has a single bit member?
Received on Fri Apr 16 13:19:39 2004

This archive was generated by hypermail 2.1.8 : Fri Apr 16 2004 - 13:19:43 PDT