RE: [sv-ac] RE: Call to vote: Due May 11

Hi Jacob,
 
I think one thing which still needs clarification is nested modules (or
interfaces if they are allowed to be nested). In case global clocking is
in a nested module, does it only apply to nested module only or it also
applies to the module where this nested module exists.
 
Thanks.
Manisha

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Katz, Jacob
Sent: Tuesday, May 17, 2011 12:56 PM
To: 'sv-ac@eda-stds.org'
Subject: [sv-ac] RE: Call to vote: Due May 11

I uploaded a slightly updated proposal for 3069, acc. to Anupam's
comment.

Changed:

Global clocking may be declared in a module, an interface, a checker, or
a program.

To:

Global clocking may be declared in a module, an interface, a checker, or
a program, including inside a generate block therein.

--------------------------------

Jacob M. Katz | jacob.katz@intel.com <mailto:jacob.katz@intel.com> |
Work: +972-4-865-5726 | iNet: (8)-465-5726

From: Prabhakar, Anupam [mailto:anupam_prabhakar@mentor.com]
Sent: Monday, May 16, 2011 21:06
To: Katz, Jacob
Subject: RE: Call to vote: Due May 11

Hi Jacob,

It does seem fine when I read it again - however I still think that the
intent is not very clear (which is why I got confused at the first
place). I think that you are proposing that a global clock can be
declared anywhere in the module as long as the elaborated design unit of
its instance has just one declaration. It is not important where it is
- where directly in the module or inside a generate (even inside a
nested module). I have rephrased your proposal with what I believe is
more simpler description of your intent - let me know what you think.

Anupam

From: Katz, Jacob [mailto:jacob.katz@intel.com]
Sent: Tuesday, May 10, 2011 2:27 PM
To: Prabhakar, Anupam; 'sv-ac@eda-stds.org'
Subject: RE: Call to vote: Due May 11

Anupam,

Why is this: "As per these rules any global clock declared inside a
generate should not apply to the parent module scope"?

I think the rules explicitly say that a global clock declared in a
generate applies to the whole module in which the generate resides. The
example shows the same thing.

Or did I misunderstand your comment?

--------------------------------

Jacob M. Katz | jacob.katz@intel.com <mailto:jacob.katz@intel.com> |
Work: +972-4-865-5726 | iNet: (8)-465-5726

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Prabhakar, Anupam
Sent: Tuesday, May 10, 2011 20:26
To: Korchemny, Dmitry; 'sv-ac@eda-stds.org'
Subject: [sv-ac] RE: Call to vote: Due May 11

Mantis 3069 ____ Yes __X__ No

http://www.eda-stds.org/mantis/view.php?id=3069

http://www.eda-stds.org/mantis/file_download.php?file_id=4971&type=bug

The proposal says

'a) Look for a global clocking declaration in the enclosing module,
interface, checker or program instance scope, or a generate block
therein. .....

b) Look for a global clocking declaration in the parent
module/interface/checker scope instance of the enclosing
module/interface/checker/program instantiation, or a generate block
therein. ....'

As per these rules any global clock declared inside a generate should
not apply to the parent module scope. However the example with a
conditional generate pulls such a default clock to the parent module
scope. I assume the functionality of this example is important and you
intend to propose that a module (or a program/interface/checker) with
elaborated generated can have only one global clock (which is also
mentioned in your proposal). The rules a) and b) should be modified to
reflect this. Note that this would also mean that a global clock
declared inside a 'for generate' would result in an error most of the
time.

Mantis 3295 __X__ Yes ____ No

http://www.eda-stds.org/mantis/view.php?id=3295

http://www.eda-stds.org/mantis/file_download.php?file_id=4978&type=bug

Friendly amendment for 3295. In the example

// disable concurrent and immediate asserts and covers for

// 20 time units. The following systask does not affect expect

// statements as control type is Off.

$assertcontrol(OFF); // using default values of all the

                     // arguments after first argument

The '... for 20 time units' is confusing as this $assertcontrol
statement has nothing to do with that. You probably should add 'After
20 time units ...' at the beginning of the comment before the next
$assertcontrol.

Anupam

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