Re: [sv-ec] Errata: join_none and automatic variable lifetimes

Stev,

You are correct. The second sentence should be more specific and either
itemize the three join mechanisms or state "all kinds of fork..join".

    Arturo

----- Original Message -----
From: "Steven Sharp" <sharp@cadence.com>
To: <sharp@cadence.com>; <sv-ec@eda.org>; <Arturo.Salz@synopsys.COM>
Sent: Tuesday, August 31, 2004 4:51 PM
Subject: Re: [sv-ec] Errata: join_none and automatic variable lifetimes

>This issue you bring up was resolved by errata # 4:
>
> http://www.eda.org/sv-ec/Errata/ERR_4.pdf
>
>Specifically, section 5.5 defines the lifetime of automatic variables declared
>within fork/join blocks to be the union of the lifetime of all the subprocesses
>spawned by that block. This definition removes the need for the restriction
>that you bring up in your message. The Verilog-2001 limitations regarding
>access to automatic variables continue to apply (e.g., access automatic
>variables via hierarchical references is not allowed).

Thanks Arturo. That does indeed address the problem. My version of the
3.1a LRM was not up-to-date with that erratum.

The newer version I downloaded says in section 5.5:

"The lifetime of a fork...join, fork...join_any, or fork...join_none block
shall encompass the execution of all processes spawned by the block. The
lifetime of a scope enclosing any fork...join block includes the lifetime
of the fork...join block."

I assume that the second sentence is intended to apply to all of the
different kinds of fork...join blocks, even though it only explicitly
mentions the first kind. This should be made clear.

Steven Sharp
sharp@cadence.com
Received on Wed Sep 1 00:40:08 2004