RE: [sv-ac] face-to-face meeting notes

Hi,
 
What is the assertion naming issue? 
 
Thanks,
Shalom


________________________________

	From: owner-sv-ac@server.eda.org
[mailto:owner-sv-ac@server.eda.org] On Behalf Of Lisa Piper
	Sent: Tuesday, October 09, 2007 3:45 AM
	To: john.havlicek@freescale.com
	Cc: sv-ac@server.eda-stds.org
	Subject: [sv-ac] face-to-face meeting notes
	
	

	

	Hi John, <<SV-AC_10_02_2007.doc>> 

	

	I have attached my meeting notes (in black text), supplemented
with Erik's meeting notes (in blue text) from the face-to-face meeting
last week.  Thanks for hosting that - I think we made a LOT of progress.

	I think the owner is obvious for most of the meeting notes with
the exception of the new (yet to be opened) Mantis items that resulted:

	

	1.      VPI access to checker instances and sequence and
properties in procedural code is an issue that needs to be addressed so
we will open an independent MANTIS item that is assigned to SV-CC (get
help from Bassam).

	2.      Adding covergroups to checkers

	3.      Assertion naming (how do you name assertions in a
function so that they can be independently enabled/disabled)

	4.      $past and other sampled valued functions outside of
concurrent assertions (that use sampled values) need to be defined. This
relates to the new glitch-free assertions that use the postponed values.

	

	We should discuss which need to be defined for the 2008 std.
Perhaps we can find owners in tomorrow's meetings.

	

	Lisa

	


	-- 
	This message has been scanned for viruses and 
	dangerous content by MailScanner <http://www.mailscanner.info/>
, and is 
	believed to be clean. 

---------------------------------------------------------------------
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.