Date: 2011-11-15

Time: 16:00 UTC (9:00 PDT)

Duration: 2 hours

Dial-in information:

Meeting ID: 38198

Phone Number(s):

1-888-813-5316 Toll Free within North America

Live Meeting:

https://webjoin.intel.com/?passcode=3934185

Agenda:

- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt

- Minutes approval

- Champions' feedback

3206: Deferred assertions are sensitive to glitches

3069: Relax rules for $global_clock resolution

3295: need a way to control only asserts/covers/assume directives

-Draft 3 review

- Opens

Attendance Record:

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

Attendance re-initialized on 2010-07-06:

n[---x-xxxxx-xxx--xxx---xxxx-xxx-xxx...........................]

Ashok Bhatt (Cadence)

n[---------xx--xxx-xxxxxx-xxxxxxxxxx-xxx-xxxxxxxxx-x-xxxxx--xxx]

Laurence Bisht (Intel)

v[-xxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxx-]

Eduard Cerny (Synopsys)

v[x-xxxxxxx-xxxxxxxxxxx--------xx---xxx--x-xxxxxxx-xxxxx-xxxxxx] Ben Cohen (Accellera)

n[------------------------------------------xx-x-xxx-x--xxxxxxx]

Surrendra Dudani (Synopsys)

n[-------------x-xxxxxx........................................]

Shaun Feng (Freescale)

v[xxxxxx---------x-x--x-x-xxxx-x-x----x-x-x--xx---xxxx---x-xxxx] Dana Fisman (Synopsys)

n[----------------------------------------xxxxx-xxxx-x-xxxxxxxx] John Havlicek (Freescale)

v[---xxxxxxxx---x-xxx-xx-xxxx-xxxxxxxxxxxxxxxx-xxx-xxxxxxxxxxxx]

Tapan Kapoor (Cadence)

n[x--xx-xxx---x-xx-xxxxx-xxxx-x-x..............................]

Jacob Katz (Intel)

t[xxxxx-xxxxxxxxx--xxx-xxxxxxxxxxxxxxxxxxxxxxx--xxxxxxxxxxxxxxx]

Dmitry Korchemny (Intel ¿ Chair)

v[x-xxx-xxxxxxxxxxx-xxxxx-xxxx-xxxxxxxxxxxxxxx--xxxxxx-xxxxxxxx]

Scott Little (Freescale)

v[xx-xxxxx-xxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxx-xxxxxxx]

Manisha Kulshrestha (Mentor Graphics)

v[x-xx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxx]

Anupam Prabhakar (Mentor Graphics)

v[x-xxxxx-xxxxxxxxx--xxx-xxxx-xxx-xxx--x-xx-xxx-xx--xxxxxxx-xxx] Erik Seligman (Intel)

v[xxxxxx-xxxxx-xxxx-xxxxxxxxxx-x-xxx-xxxx-xxxx--xxxxxx-xxxxxxx.]

Samik Sengupta (Synopsys)

v[xxxxxxxxxxx-xxxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxxxxxx-xxx] Tom Thatcher (Oracle ¿ Co-Chair)

n[-------------------------xx---xx-------x.....................]

Srini Venkataramanan (CVC Pvt Ltd)

n[---------------x.............................................]

Vibarajan Viswanathan (Marvell)

|- attendance on 2011-11-15

|--- voting eligibility on 2011-11-15

Minutes

- Reminder of IEEE patent policy.

See: http://standards.ieee.org/board/pat/pat-slideset.ppt

Participants were reminded of the IEEE Patent Policy

- Minutes approval

Erik: Move to approve minutes

Ben: Second

Vote results: 8y, 0n, 0a

- Champions' feedback

3206: Deferred assertions are sensitive to glitches

Erik: Has uploaded a new proposal

Erik: Move to approve new revised proposal

Samik: Second

Vote results: 8y, 0n, 0a

3069: Relax rules for $global_clock resolution

(No new proposal has been updated)

Jakob: Champion members have not responded to explanations of the proposal.

There were a few back-and-forth e-mails with Francoise, but still

no indication that all her concerns are answered.

Shalom was concerned about rules for searching for global_clk

Rules are similar to rules for searching for identifiers

But global clock is not an identifier, so rules could be different.

Jakob: We should wait for response to see what the Champions say.

Ben: Can I declare inside a package?

Jakob: Proposal only allows global clocking definition inside modules.

Ben: But a package is imported into a module. Wouldn't the global

clocking take effect in that module?

Jakob: Could the signal referred to by the global clocking be defined in

a package?

Anupam: We allow only one global clocking for an elaborated module.

(Dmitry Joined)

Anupam: In the future, if you wanted to be able to encapsulate something

within a generate, it would be backward incompatible.

Tom: Originally, we had one global_clocking allowed for the entire

elaborated design. That wasn't flexible enough. Now we allow one

global_clocking per module.

Will we need to relax the rules later to allow different

global_clocking?

Jakob: Here's why we wanted global clocking definition inside generate to

apply to the whole module:

Say you used parameter values to set the global_clocking. You would

have a generate block with an if:

parameter P

generate

if (P==1) begin

global clocking x

end

else begin

global clocking y

end

endgenerate

The remainder of the module logic would be outside the generated,

but you would want the global clocking to apply.

Manisha: Originally, default clocking had no rules for generate. We

didn't want to have the same problem with global clocking. Thats

why we defined rules for global clocking within generate.

Dmitry: Maybe we just don't define global clocking within generate blocks.

(or don't allow)

Manisha, Anupam: You could use the following alternative to set

global clocking from parameter:

parameter P

generate

if (P==1) begin:b1

assign gen_clk = clk1

end

else begin:b1

assign gen_clk = clk2

end

endgenerate

global_clocking b1.gen_clk

The block names for the conditionals should be named the same.

(They are allowed to be the same by the standard).

Then user can refer to "b1" without knowing which branch of the

if will be generated.

Anupam: This is probably a better solution.

Anupam: Then disallow global clocking within generate for now.

Dmitry: We need to get the proposal amended quickly

Dmitry: Will call for an slightly shorter e-mail vote (5 days) after

proposal is updated.

3295: need a way to control only asserts/covers/assume directives

(No new proposal has been updated)

Manisha: Brad's objection: passing integers for function parameter

instead of using enumerated types (He gave an example of some

other type of system function that does this).

Manisha: E-mailed Brad: He is fine with integers for now.

Francoise has not responded.

Tom: Don't understand Francoise's comment. We already have $assert_on,

$assert_off, which turn assertions on and off. The new functions

only allow more selection possibilities.

Dmitry: Since Brad agreed to accecpt integers, will simply move item back

to resolved state, and send it back to Champions.

-Draft 3 review

Dmitry: Reminder: if you see issues with implementation move issue into

editor state.

Anupam: One issue, we had thought we could make a simple change in the

editing.

Dmitry: We'll need to open a new Mantis item for this. We may need to

address this in ballot comments.

- Opens

Meeting adjourned.