Hi Manisha,
Let’s close this issue at the next meeting. If we agree with your suggestion I will remove the first line.
Thanks,
Dmitry
From: Kulshrestha, Manisha [mailto:Manisha_Kulshrestha@mentor.com]
Sent: Monday, September 19, 2011 07:59
To: Korchemny, Dmitry; sv-ac@eda-stds.org
Subject: RE: [sv-ac] Call to vote: Due September 12
Hi Dimitry,
I still do not see the consistency in the rules for inferring the data type ( I am looking at latest PDF).
Currently it says:
¾ If the argument has an explicit direction qualifier input, it is assumed to be untyped.
Otherwise, if the argument has an explicit direction qualifier, it shall be an error to omit its type.
This is inconsistent. If the user is specifying a direction, it should be illegal to omit the data type. If user wants to make it untyped, that is possible for him by typing untyped.
Thanks.
Manisha
From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com]
Sent: Wednesday, September 14, 2011 11:21 PM
To: Kulshrestha, Manisha; sv-ac@eda-stds.org
Subject: RE: [sv-ac] Call to vote: Due September 12
Hi Manisha,
Please, see my comments below.
Thanks,
Dmitry
From: Kulshrestha, Manisha [mailto:Manisha_Kulshrestha@mentor.com]
Sent: Tuesday, September 13, 2011 09:02
To: Korchemny, Dmitry; sv-ac@eda-stds.org
Subject: RE: [sv-ac] Call to vote: Due September 12
Mantis 2093 ____ Yes __X__ No
http://www.eda-stds.org/mantis/view.php?id=2093 <http://www.eda-stds.org/mantis/view.php?id=2093%20>
http://www.eda-stds.org/mantis/file_download.php?file_id=5345&type=bug
Here are the comments:
1. I don’t understand the reason for creating list_of_checker_port_identifiers in bnf. Only thing which is needed is to add optional checker_port_direction.
[Korchemny, Dmitry] Updated the BNF.
2. I do not like the way data type is getting inferred in section 17.2. It is not consistent. If we are making it mandatory to specify type if user has keyword ‘output’ then it should be mandatory to put type if ‘input’ is used. This will make it consistent with ‘local…’ type of arguments for properties. If we do not want to make it mandatory then it should infer data type from the previous declaration instead of making it untyped.
[Korchemny, Dmitry] Updated the rule to handle input and output the same way.
3. In the sentence “Similarly to sequences and properties a checker declaration…”, I think it should be ‘Similar to sequence and property declarations, a checker …..”.
[Korchemny, Dmitry] I think “similarly” is correct here, there are many examples in the LRM.
4. There is no clarification about how output port initialization is done. Does it happen in reactive region ?
[Korchemny, Dmitry] The output port initialization shall occur before any initial or always procedures are started, as explained in 6.8. I added the following sentence:
Checker output port initialization has the same semantics as a variable initialization (see 6.8).
5. Since actual connected to output port of a checker is going to get updated in reactive region, it may be good to show an example how to use this value. Current examples only show the checkers but do not show how to read that value in testbench to get updated value.
[Korchemny, Dmitry] Added an example.
Manisha
---------------------------------------------------------------------
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, and is believed to be clean.Received on Sun Sep 18 23:09:04 2011
This archive was generated by hypermail 2.1.8 : Sun Sep 18 2011 - 23:09:09 PDT