RE: [sv-ac] changes in 1729 due to 1641

Hello Manisha and all,
 
please find attached a first draft of the updated proposal 1729
(immediate assume and cover) in which I try to align it with 1361 and
1461. Have a look and let me know if this is the right direction to
follow. Since there are many changes in the two preceding proposal,
imposing the new ones and remaining consistent is not obvious. It would
almost be better to rewrite the sections16.3 and possibly other ones.
 
Best regards,
ed
 


________________________________

	From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf
Of Kulshrestha, Manisha
	Sent: Tuesday, November 06, 2007 1:07 AM
	To: sv-ac@eda.org
	Subject: [sv-ac] changes in 1729 due to 1641
	
	

	Hi Ed,

	 

	Here are the changes required in 1729 due to changes in 1641.
Please refer to 1641 along with this email to make sure everything looks
fine. Probably you want to change the proposal such that it shows two
set of changes (one in the current form and others with the approval of
1641 by champions).

	 

	1.       The following will be changed.

	 

	The immediate assert statement immediate_assertion_statement is
a statement_item and can be specified anywhere a procedural statement is
specified. The execution of immediate assertions can be controlled by
using assertion control system tasks (See 19.10).

	 

	2.       Your proposal does not take into account changes in
this section due to 1361. Since you have a separate paragraph about
immediate covers, there also you need to mention about assertion action
control tasks.

	3.       The changes in the following part are not needed as it
is deleted in 1461.

	 

	Because the assertion An immediate assert, or an immediate
assume being checked in the same manner as

	an immediate assert, is a statement that something must be
true,. Therefore, the failure of an assertion

	immediate assert or assume shall have a severity associated with
it. By default, the this severity of an

	assertion failure is shall be error. 

	 

	4.       The following statement has changed too:

	If an assertion immediate assert or assume fails and no else
clause is specified, the tool shall, by default, call $error, unless a
tool-specific option, such as a command-line option, is enabled to
suppress the failure.

	 

	5.       The following is deleted:

	All of these severity system tasks shall print a tool-specific
message indicating the severity of the failure and

	specific information about the specific failure, which shall
include the following information:

	- The file name and line number of the assertion immediate
assert or assume statement.

	- The hierarchical name of the assertion immediate assert or
assume, if it is labeled, or the scope of

	the assertion immediate assert or assume if it is not labeled.

	For simulation tools, these tasks shall also include the
simulation run time at which the severity system task

	is called.

	Each system task can also include additional user-specified
information using the same format as $display.

	 

	6.       The following line has changed:

	If more than one of these system tasks is included in the else
clause, then each shall be executed as specified.

	 

	Thanks.

	Manisha


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


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