[sv-cc] Draft4 errata

Subject: [sv-cc] Draft4 errata
From: Bassam Tabbara (bassam@novas.com)
Date: Fri Jan 23 2004 - 17:54:47 PST

• Next message: David W. Smith: "[sv-cc] Draft 4 change verification"
• Previous message: Swapnajit Mittra: "Re: [sv-cc] vpi_diagrams-1-23-2004.pdf"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Joao,
 
The one thing that seems missing is item (2) in my email below, I think we
need to add one more figure *LIKE* this one:

But with "multiclock property expr" -->> clocked property. Right ?
 
Can you squeeze that in and send to David again, seems this would add the
"multiclock property" support. (30.3 seems a bit empty I think you can throw
this in there).
 
Thx.
-Bassam.

--
Dr. Bassam Tabbara
Technical Manager, R&D
Novas Software, Inc.
http://www.novas.com <http://www.novas.com/> 
(408) 467-7893 
-----Original Message-----
From: Bassam Tabbara [mailto:bassam@novas.com] 
Sent: Monday, January 19, 2004 2:29 PM
To: 'Joao.Geada@synopsys.com'
Cc: 'sv-cc@server.eda.org'
Subject: RE: [sv-cc] Today's SV VPI Update
Joao, [this is an html email so I can paste the fixes ...]
My apologies for this oversight on my part, somehow I never sent the first
part out of this email earlier ... sorry about that. A couple of
enhancements remain in the property part, here's what I see (in the rev you
just sent out) to more accurately reflect draft3 (most are just additions
similar to what you have already, so not a big issue, nothing is wrong, just
need a bit more beef up ...): As far as I can tell this all I see.
PART I: Diagrams
1) vpiPropertyOpType needs to also have: vpiAnd,  vpiOR, and if/else , see
the following (draft3)
property_expr ::=
sequence_expr
| ( property_expr )
| not property_expr
| property_expr or property_expr
| property_expr and property_expr
| sequence_expr |-> [ not ] sequence_expr property_expr
| sequence_expr |=> [ not ] sequence_expr property_expr
| if ( expression ) property_expr [ else property_expr ]
| property_instance
2) property expr needs to also have "multiclock property expr" before/under
property expr, and then a new diagram for "multiclock property expr"  of the
form (similar to property expr)
multi_clock_property_expr ::=
property_expr
! multi_clock_sequence
| clocking_event multi_clock_property_expr
| ( multi_clock_property_expr )
| not multi_clock_property_expr
| multi_clock_property_expr or multi_clock_property_expr
| multi_clock_property_expr and multi_clock_property_expr
| multi_clock_sequence |-> multi_clock_property_expr
| multi_clock_sequence |=> [ not ] multi_clock_sequence
multi_clock_property_expr
| if ( expression ) multi_clock_property_expr [ else
multi_clock_property_expr ]
| property_instance
3) Multi clock sequence expression also needs some enhancements (top figure
in below, needs to be more enhanced with "ops" too 
 
Add the following:
multi_clock_sequence::=
clocked_sequence { ## clocked_sequence }
sequence_expr
| clocking_event multi_clock_sequence
| ( multi_clock_sequence )
| multi_clock_sequence ## multi_clock_sequence
PART II: vpi_user.h: missing the assertion/coverage/Read VPI... what's the
plan for this ? 
Thx.
-Bassam.

• image/bmp attachment: Outlook.bmp

• image/bmp attachment: Outlook.bmp

• image/bmp attachment: Outlook.bmp

• image/bmp attachment: Outlook.bmp

• Next message: David W. Smith: "[sv-cc] Draft 4 change verification"
• Previous message: Swapnajit Mittra: "Re: [sv-cc] vpi_diagrams-1-23-2004.pdf"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b28 : Fri Jan 23 2004 - 18:22:19 PST