RE: [sv-ac] Updated proposal for 1641 (severity system tasks)

Hi all,

 

I would create another mantis for it. It may take much time to converge.

 

Dmitry

 

________________________________

From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of Kulshrestha, Manisha
Sent: Monday, March 12, 2007 11:32 PM
To: Miller Hillel-R53776; sv-ac@server.eda-stds.org
Subject: RE: [sv-ac] Updated proposal for 1641 (severity system tasks)

 

Hi,

The chapter 17 disusses having tool specific switches to control info
and warning messages. But there is no system task to do that.

Does it have to be part of this proposal or we can create another mantis
for that ?

Manisha


-----Original Message-----
From: Miller Hillel-R53776 [mailto:r53776@freescale.com]
Sent: Sat 3/10/2007 8:02 PM
To: Kulshrestha, Manisha; sv-ac@eda-stds.org
Subject: RE: [sv-ac] Updated proposal for 1641 (severity system tasks)

Hi,

I was wondering whether it made sense to add
$severityreportoff/$severityreportoff capabilities.

In the assertion case we could switch things "completely off" and things
would not be reported using $assertoff.

There may be a need for this after expanding to everything. Also it is a
good opputunity to have some priority control over the types of messages
reported.

This needs to be sent to other commitees.

Thanks, Hillel


________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Kulshrestha, Manisha
Sent: Saturday, March 10, 2007 1:22 AM
To: sv-ac@eda-stds.org
Subject: [sv-ac] Updated proposal for 1641 (severity system tasks)


Hi,

I have updated a proposal based on the discussion in the meeting. This
proposal does not distinguish usage of these tasks in assertion vs.
regular sequential code. All the information is printed based on where
the severity task is called.

Please send your feedback.

As we discussed in the meeting how a user can print information about
assertion from these tasks if the task is not directly inside action
block. Here is an example about how a task can be called from an action
block and print the error messages. I did not find any standard way for
these tasks to print file name and line number of the assertion
statement (although there are tool specific ways to do that). Hopefully
in future it will be possible in System Verilog itself. Here is an
example:

module test;

reg clk;
reg a;
reg [127:0] name;

initial
begin
 clk = 0;
 a = 0;
end

always #10 clk = ~clk;

MYASSERT:assert property (@(posedge clk) a) else
begin
   $swrite(name, "%m");
   myTask(name);
end

task automatic myTask(ref reg [127:0] assertName);
begin
   $error($time, ": assert %s failed", assertName);
end
endtask

endmodule

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