Subject: A.7.5.3: scalar_timing_check_expressions has redundancies
From: Shalom.Bresticker@motorola.com
Date: Sun Dec 29 2002 - 05:13:13 PST
>Category: errata
>Synopsis: A.7.5.3: scalar_timing_check_expressions has redundancies
>Confidential: no
>Severity: non-critical
>Priority: low
>Class: errata-discuss
>Submitter-Id: etf
>Originator: Dan.Jacobi@intel.com
>Release: 2001b: A.7.5.3
>Environment:
See SV-BC19-41,42
>Description:
This is from Dan Jacobi.
scalar_timing_check_condition ::=
expression
| ~ expression
| expression == scalar_constant
| expression === scalar_constant
| expression != scalar_constant
| expression !== scalar_constant
The last 5 rules are redundant due to the fact that they all
can be parsed by parsing the expression token.
The main intention might have been to use the syntactic
category 'primary' instead of 'expression' in all the
above rules.
In this case we wouldn't need to strike out the specified
rules.
This issue is labeled as SV-BC-19-42.
This issue is related to the IEEE-1364 standard.
timing_check_condition ::=
scalar_timing_check_condition
| ( scalar_timing_check_condition )
Assuming the previous fix is correct,
then the brackets can be added when parsing the token
'expression', therefore the removed rule is redundant.
This issue is labeled as SV-BC-19-41.
This issue is related to the IEEE-1364 standard.
>How-To-Repeat:
>Fix:
>Unformatted:
This archive was generated by hypermail 2b28 : Sun Dec 29 2002 - 05:13:41 PST