[sv-bc] RE: [sv-ac] assert inside fork....join

Section 16.15 says concurrent assertions are limited to always and
initial procedures as a statement. 

Section 16.15.6 says this about clock inference

1) There is no blocking timing control in the procedure.
2) There is exactly one event control in the procedure.

Making the use of fork/join useless.

It seems to me and from other text in the whole section that the use of
term "procedure" is being used to mean a "process"; more specifically a
synthesizable combinational or sequential process.

Given that the LRM currently restricts concurrent assertions from tasks
and functions, I doubt any consideration was made to the semantics of
fork...join/join_any used with a concurrent assertion.



Dave



> -----Original Message-----
> From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org]
On
> Behalf Of Bresticker, Shalom
> Sent: Monday, November 24, 2008 10:52 PM
> To: soumya; sv-ac@server.eda.org; sv-bc@server.eda.org
> Subject: RE: [sv-ac] assert inside fork....join
> 
> I can't see anything to forbid it.
> 
> Shalom
> 
> > -----Original Message-----
> > From: owner-sv-ac@server.eda.org
> > [mailto:owner-sv-ac@server.eda.org] On Behalf Of soumya
> > Sent: Tuesday, November 25, 2008 8:54 AM
> > To: sv-ac@server.eda.org
> > Subject: [sv-ac] assert inside fork....join
> >
> > Hi,
> > Is it legal to declare assert/cover statement inside fork...join ?
> >
> > initial
> > fork
> > prop1 : assert property(prop);
> > cover1 : cover property(prop);
> > join
> >
> > Thanks,
> > -Soumya
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.