Re: [sv-ec] erratum 173

Francoise,

When specified as part of the covergroup declaration, an option is like
a constant declaration and hence part of the declaration. Note that
the covergroup declaration defines neither an execution context
nor an execution order for the items declared within it. Consider the
following simple example:

    covergroup cg @(posedge clk) ;
        coverpoint a
        {
            option.auto_bin_max = 2;
            option.auto_bin_max = 5;
        }
        coverpoint b ;
    endgroup

The example shows a covergroup declaration, which does not execute
until an object of type cg is instantiated. Likewise, there is no execution
order stipulated by the two definitions (coverpoint a and b). Because the
option declaration is a constant declaration, it has the same semantics
as the following declaration:

    const logic flag = 1 ;
    const logic flag = 0 ;

And, the code above will also result in an error.

    Arturo

----- Original Message -----
From: Francoise Martinolle
To: sv-ec@eda.org
Sent: Friday, October 01, 2004 12:06 PM
Subject: [sv-ec] erratum 173

Arturo,
I do not understand why option.auto_bin_max = 100; is considered a declaration.
option is a built-in member of every coverage group, it is of a struct type and auto_bin_max is one of the
struct field.
For me this looks a lot like a procedural statement.
Can you explain why you think that this is a declaration?

Francoise
       '
Received on Fri Oct 1 15:43:46 2004