Subject: Re: [sv-ac] Conflict in Sv3.1 LRM
From: Peter Flake (Peter.Flake@synopsys.com)
Date: Wed Nov 19 2003 - 04:46:19 PST
Hi Kausik,
The SV-BC has removed statement_or_null from description.
Regards,
Peter.
At 17:23 17/11/2003 +0530, Kausik Datta wrote:
>Hi,
>Here is a conflict of assertion related rules in BNF.
>Thanks
>Kausik
>
>Consider the following rules -
>
>description ::= statement_or_null
> | module_root_item
> | ....
>
>statement_or_null can contain procedural_assertion_item.
>
>procedural_assertion_item :: = immediate_assert_item
> | assert_property_statement
> | cover_property_statement
>
>again, module_root_item can contain concurrent_assertion_item
>
>concurrent_assertion_item
> ::= [block_identifier] assert_property_statement
> | [block_identifier] cover_property_statement
> | .....
>
>So, if someone writes the rule assert_property_statement in the root
>scope, then there is a conflict. assert_property_statement can be derived
>from statement_or_null rule as well as from module_root_item.
>
>same thing happens if someone writes the rule cover_property_statement in
>root scope.
>
>
>
This archive was generated by hypermail 2b28 : Wed Nov 19 2003 - 04:55:20 PST