RE: [sv-ac] [sv=ac] 23.2.4, 23.11 Binding a checker to an interface // contradictory??

Found it.

Mantis 1900, which introduced checkers, also added the words "or a checker_instantiation" in this footnote.

This giant Mantis was implemented in Draft 7 of P1800-2009.

The change referenced the wrong Syntax excerpt for what is now Syntax 23-5, and somehow in all the reviews no one noticed.
The change was thus not implemented for this syntax excerpt, and the error was in 1800-2009 and was not pointed out till now.

It should be possible to correct this error in the recirculation ballot.

Thanks for pointing out the inconsistency.

Regards,
Shalom

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Bresticker, Shalom
Sent: Monday, August 13, 2012 14:50
To: hdlcohen@gmail.com; sv-ac@eda-stds.org
Subject: RE: [sv-ac] [sv=ac] 23.2.4, 23.11 Binding a checker to an interface // contradictory??

Now I got access to the LRM.

Footnote 4 in Syntax 23-5 says,

"4) If the bind_target_scope is an interface_identifier or the bind_target_instance is an interface_instance_identifier,
then the bind_instantiation shall be an interface_instantiation."

In Syntax 23-9 and in A.10, it says,

"4) If the bind_target_scope is an interface_identifier or the bind_target_instance is an interface_instance_identifier,
then the bind_instantiation shall be an interface_instantiation or a checker_instantiation."

I will check what happened.

Shalom

From: owner-sv-ac@eda.org<mailto:owner-sv-ac@eda.org> [mailto:owner-sv-ac@eda.org]<mailto:[mailto:owner-sv-ac@eda.org]> On Behalf Of Bresticker, Shalom
Sent: Monday, August 13, 2012 10:30
To: hdlcohen@gmail.com<mailto:hdlcohen@gmail.com>; sv-ac@eda-stds.org<mailto:sv-ac@eda-stds.org>
Subject: RE: [sv-ac] [sv=ac] 23.2.4, 23.11 Binding a checker to an interface // contradictory??

Hi, Ben.

I don't have access at the moment to the LRM, but according to what you have quoted, the answer is clearly NO.
You have quoted the BNF, but the BNF of the bind_directive explicitly points you to Footnote 4, which restricts binding to interfaces.
More generally, the BNF is supplemented by the text of the LRM, as we have discussed many times.

I can't tell you at the moment what was the reason for the restriction.

Regards,
Shalom

From: owner-sv-ac@eda.org<mailto:owner-sv-ac@eda.org> [mailto:owner-sv-ac@eda.org]<mailto:[mailto:owner-sv-ac@eda.org]> On Behalf Of Ben Cohen
Sent: Monday, August 13, 2012 07:40
To: sv-ac@eda-stds.org<mailto:sv-ac@eda-stds.org>; Korchemny, Dmitry; Seligman, Erik; Prabhakar, Anupam
Subject: [sv-ac] [sv=ac] 23.2.4, 23.11 Binding a checker to an interface // contradictory??

 Question: Can I bind a checker to an interface?
Section 23.2.4 seems to say NO because if the target scope is an interface, then the bind instantiation shall be an interface identifier.
But
23.11 says YES
Am I reading this wrong?
I understood that you can bind a checker to an interface.
Ben
---------
23.2.4 Module contents
4) If the bind_target_scope is an interface_identifier or the bind_target_instance is an interface_instance_identifier,
then the bind_instantiation shall be an interface_instantiation.
Syntax 23-5-Module item syntax (excerpt from Annex A)

23.11 Binding auxiliary code to scopes or instances
bind_directive4 ::= // from A.1.4
  bind bind_target_scope [: bind_target_instance_list] bind_instantiation ;
  | bind bind_target_instance bind_instantiation ;
bind_target_scope ::=
  module_identifier
  | interface_identifier
bind_target_instance ::=
  hierarchical_identifier constant_bit_select
bind_target_instance_list ::=
   bind_target_instance { , bind_target_instance }
bind_instantiation ::=
  program_instantiation
  | module_instantiation
  | interface_instantiation
  | checker_instantiation

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