From: Charles Dawson (chas@cadence.com)
Date: Mon May 19 2003 - 10:08:50 PDT
Precedence: bulk
-------- Original Message --------
From: "David J. Roberts" <roberts>
Subject: 237 issue
To: chas
The proposal wants to allow arbitrary conditions to be used in tcheck
conditions. This is to be done by changing
REPLACE:
scalar_timing_check_condition ::=
expression
| ~ expression
| expression == scalar_constant
| expression === scalar_constant
| expression != scalar_constant
| expression !== scalar_constant
WITH:
scalar_timing_check_condition ::=
expression
REPLACE:
timing_check_condition ::=
scalar_timing_check_condition
| ( scalar_timing_check_condition )
WITH:
timing_check_condition ::=
scalar_timing_check_condition
There is no mention in the proposal as to whether or not the paragraph
following the BNF containing the following text should be modified.
If more then one condition signal is required for conditioning
timing checks, appropriate logic shall be combined in a separate
signal outside the specify block, which can be used as the
conditioning signal.
The intent of the BNF modification appears to be to allow for
complete arbitrary expressions to be used in the tcheck condition.
But section 15.6 as shown above has a paragraph that still limits the
type of expression that can be used. If this is the case then the
proposed BNF changes are not correct.
--David Roberts
This archive was generated by hypermail 2.1.4
: Mon May 19 2003 - 10:09:36 PDT
and
sponsored by Boyd Technology, Inc.