[sv-ac] RE: sv-ac 1531

Doron,

I would be for leaving the semantics as loose as possible, in other
words, if the user writes to a global variable from two parallel
processes, there is nothing in the language to stop him/her. Why do we
have to policy it in the assertios? As I said earlier, if I use tasks, I
can do this today, but it is cumbersome. 

ed
 

> -----Original Message-----
> From: Doron Bustan [mailto:dbustan@freescale.com] 
> Sent: Thursday, July 13, 2006 6:27 PM
> To: Eduard Cerny
> Cc: sv-ac@eda-stds.org
> Subject: sv-ac 1531
> 
> Ed,
> 
> we need a  definition of a semantic for static local variables.
> In particular it make sense to define different flow rules
> for static local variables.
> 
> for example
> 
> property p1;
> logic [3:0] v;
> 
> ((a, v = 1) or (b, v=2)) ##1 (v == 1);
> endproperty
> 
> is legal, but
> 
> property p2;
> static logic [3:0] v;
> 
> ((a, v = 1) or (b, v=2)) ##1 (v == 1);
> endproperty
> 
> probably should not be legal, because the value of v flowing 
> out of ((a, 
> v = 1) or (b, v=2)) is undefined.
> 
> BTW, I think that initialization should be in a separate proposal.
> 
> Doron
>