RE: [sv-ac] RE: call to vote on 2250

From: Bassam Tabbara <Bassam.Tabbara_at_.....>
Date: Mon Feb 04 2008 - 14:52:33 PST
Hi Dmitry,

vpiSequenceOp does not cut it in my mind -- there is no operator here
(the operator is the "top operator" of sequence_expr). How about we just
live with the explanation of how the qualifier applies to the sequence
expression ...

Bottom line: I suggest to strike out the vpiSequenceOp and modify (3) to
be something like:

"3) vpiOpStrong is valid only for operations vpiNextOp, vpiAlwaysOp,
vpiEventuallyOp, vpiUntilOp,
vpiUntilWithOp and for the sequence expression *operation*. vpiOpStrong
shall return TRUE to indicate the strong version of the corresponding
operator."

May be Lisa's comment was just because she missed "and for the sequence
..." in the first place ?

Thx.
-Bassam.

-----Original Message-----
From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com] 
Sent: Monday, February 04, 2008 4:59 AM
To: Bassam Tabbara; piper@cadence.com; john.havlicek@freescale.com;
sv-ac@eda.org; yaniv.fais@freescale.com
Cc: Bustan, Doron; eduard.cerny@synopsys.COM;
Manisha_Kulshrestha@mentor.com; johan.martensson@jasper-da.com;
Seligman, Erik; thomas.thatcher@sun.com
Subject: RE: [sv-ac] RE: call to vote on 2250

Hi Lisa, Bassam,

I added a new opcode vpiSequenceOp (see the attachment to my previous
mail, also uploaded into Mantis). This should allow using weak/strong
qualifiers with sequences as well. Would it work?

Thanks,
Dmitry

-----Original Message-----
From: Bassam Tabbara [mailto:Bassam.Tabbara@synopsys.com]
Sent: Thursday, January 31, 2008 8:53 PM
To: piper@cadence.com; Korchemny, Dmitry; john.havlicek@freescale.com;
sv-ac@eda.org; yaniv.fais@freescale.com
Cc: Bustan, Doron; eduard.cerny@synopsys.COM;
Manisha_Kulshrestha@mentor.com; johan.martensson@jasper-da.com;
Seligman, Erik; Bassam.tabbara@synopsys.COM; thomas.thatcher@sun.com
Subject: Re: [sv-ac] RE: call to vote on 2250

As far as the range question below, I think it is just an optimization,
I don't recall the details but surely we can simply return the operand.

Thx. 
-Bassam

----- Original Message -----
From: Lisa Piper <piper@cadence.com>
To: Korchemny, Dmitry <dmitry.korchemny@intel.com>;
john.havlicek@freescale.com <john.havlicek@freescale.com>; sv-ac@eda.org
<sv-ac@eda.org>; yaniv.fais@freescale.com <yaniv.fais@freescale.com>
Cc: Bustan, Doron <doron.bustan@intel.com>; eduard.cerny@synopsys.COM
<eduard.cerny@synopsys.COM>; yaniv.fais@freescale.com
<yaniv.fais@freescale.com>; Manisha_Kulshrestha@mentor.com
<Manisha_Kulshrestha@mentor.com>; johan.martensson@jasper-da.com
<johan.martensson@jasper-da.com>; erik.seligman@intel.com
<erik.seligman@intel.com>; bassam.tabbara@synopsys.COM
<bassam.tabbara@synopsys.COM>; thomas.thatcher@sun.com
<thomas.thatcher@sun.com>
Sent: Thu Jan 31 09:54:29 2008
Subject: RE: [sv-ac] RE: call to vote on 2250

I see the strong operator qualifier but not strong sequence (keywords
strong(sequence_expr) and weak(sequence_expression) ). Aren't they
different?

Lisa

-----Original Message-----
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Korchemny, Dmitry
Sent: Thursday, January 31, 2008 12:49 PM
To: Lisa Piper; john.havlicek@freescale.com; sv-ac@eda.org;
yaniv.fais@freescale.com
Cc: Bustan, Doron; eduard.cerny@synopsys.com; yaniv.fais@freescale.com;
Manisha_Kulshrestha@mentor.com; johan.martensson@jasper-da.com;
erik.seligman@intel.com; bassam.tabbara@synopsys.com;
thomas.thatcher@sun.com
Subject: RE: [sv-ac] RE: call to vote on 2250

Hi Lisa, Yaniv,

I am attaching a new version, but I haven't uploaded it into Mantis,
since I am not sure that I addressed all your comments there. If you
agree with my understanding, I will upload this version.

Please, see my notes below.

Thanks,
Dmitry


-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of Lisa Piper
Sent: Thursday, January 31, 2008 4:32 PM
To: john.havlicek@freescale.com; sv-ac@server.eda.org
Cc: Bustan, Doron; eduard.cerny@synopsys.com; yaniv.fais@freescale.com;
Korchemny, Dmitry; Manisha_Kulshrestha@mentor.com;
johan.martensson@jasper-da.com; Seligman, Erik;
bassam.tabbara@synopsys.com; thomas.thatcher@sun.com
Subject: [sv-ac] RE: call to vote on 2250

I vote yes with the following friendly amendments:

1. Shouldn't "vpiImplies" and "vpiIff" be added to the list of
vpiOpTypes for a property?

[Korchemny, Dmitry] Added (see attachment).

2. Don't we need a "strong" and a "weak" operator for sequence
expressions?

[Korchemny, Dmitry] I assume that weak is the same as just a sequence
expression, and strong is a sequence expression with the qualifier
vpiOpStrong, since weak and strong do not characterize the sequence
expression, but the property.

3. For vpiNextOp, why are we giving a constant only if different than 1?
I know for arguments, the default value is returned when a specific
value is not provided. So perhaps we should return the default "1" when
none exists. This would also make it predictable that a constant will
always follow next.  (also, I think the terminology "returned" is better
than "given")

[Korchemny, Dmitry] I tried to be consistent with the sequence
expressions (see 36.47). It is written there:

"vpiUnaryCycleDelayOp: Arguments shall be: sequence, left range, right
range. Right range shall only be given if different from left range."

What does it exactly mean: is it an error to specify the right range if
it coincides with the left range, or just it is legal to omit the right
range in this case?

I didn't find in Clause 36 any case with explicitly specified default
value.

Lisa
-----Original Message-----
From: John Havlicek [mailto:john.havlicek@freescale.com]
Sent: Tuesday, January 29, 2008 10:29 PM
To: sv-ac@eda.org
Cc: doron.bustan@intel.com; eduard.cerny@synopsys.com;
yaniv.fais@freescale.com; john.havlicek@freescale.com;
dmitry.korchemny@intel.com; Manisha_Kulshrestha@mentor.com;
johan.martensson@jasper-da.com; Lisa Piper; erik.seligman@intel.com;
bassam.tabbara@synopsys.com; thomas.thatcher@sun.com
Subject: call to vote on 2250

Hi Folks:

This is the call to vote on the proposal for Mantis 2250.

The document on Mantis is 

   2250_LTL_VPI_080127dk.pdf

Please vote if you are eligible.  See details below.

J.H.

------------------------------------------------------------------------
----------
Ballot on Mantis 2250

- Called on 2008-01-29, final ballots due by 2008-02-04 T 23:59-08:00.

 v[xxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx-xx] Doron Bustan
(Intel)
 v[xxxxxxx--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-x] Eduard Cerny
(Synopsys)     
 n[------------------------x-xxx---------x-x-xxx-x---x] Surrendra Dudani
(Synopsys)
 v[-xxxxxxxxx-xxxxxx-xxxxxxxxx-xx-xxxxx-xxx-xxx-------] Yaniv Fais
(Freescale)
 t[xxxxxx--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] John Havlicek
(Freescale - Chair)
v[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxrxxxxxxxxxxxxx-xxx] Dmitry Korchemny
(Intel - Co-Chair)
v[xxxxxxx-xxxxxxxxx-xxx-x--xx--xxxxx----------xx-xxxx] Manisha
Kulshrestha (Mentor Graphics)
n[-x-------------------------------------------------] Ah-Lam Lee
(Qualcomm)
 n[--------------------------------xxxxx-------x-xx-x-] Jiang Long
(Mentor Graphics)
n[-----------x------------x--xxx.....................] Joseph Lu
(Altera)
 n[--xxxxxxxxxxxxxxxxxxx..............................] Johan Martensson
(Jasper)
 n[-----------------------------x--x-xx--xx-xxxxxxx-x-] Hillel Miller
(Freescale)
 v[xxxxxxx-xxxx-xxxxxxxxxxxxxxxxxxx-xxxxxxxx-xxxxxxxxx] Lisa Piper
(Cadence)
 v[xxxxxxxx-x-x-xx-xxxxxxx-x-xxxxx-x..................] Erik Seligman
(Intel)
 n[---------x-x----x--------xxxx-----xxxx-xx----------] Tej Singh
(Mentor Graphics)
v[x-xxxxxx-x-xxxxxx--xxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxx] Bassam Tabbara
(Synopsys)
 v[xxxxxxxxxxx-xxxxxxxxxxxxx-xxxxxxxxxx...............] Tom Thatcher
(Sun Microsystems)
   |--------------------------------------------------- attendance on
2008-01-29
 |----------------------------------------------------- voting
eligibility for this ballot
|------------------------------------------------------ e-mail votes
received

        Legend:
                x = attended
                - = missed
                r = represented
                . = not yet a member
                v = valid voter (2 out of last 3 or 3/4 overall)
                n = not a valid voter
                t = chair eligible to vote only to make or break a tie

--
This message has been scanned for viruses and dangerous content by
MailScanner, 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.

---------------------------------------------------------------------
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.
Received on Mon Feb 4 14:53:03 2008

This archive was generated by hypermail 2.1.8 : Mon Feb 04 2008 - 14:53:50 PST