Meeting Time: Monday, 25th of November, 9-11am Pacific
Call-in information is:
PARTICIPANT
CODE: 516134
Toll Free Dial In Number: (877)233-7845
International Access/Caller Paid Dial In Number: (505)766-5458
Agenda for the
Main goal is to have the bulk of issues resolved by
second week of February.
Ø
Karen and
Johny need to present the static proposal to Vassilios.
Johny to ask Vassilios to speak with
Peter before Friday.
Ø
We need
to start a new section of things that need to be added
to 1364. %u or %v on
structure types for example? Karen will
add an item to the issues list.
Ø
Karen
will present some issues to the ETF: SV-BC19-6, SV-BC19-15
Ø
Everyone
needs to consider solutions for 11/25 Meeting: SV-BC19-7,
SV-BC19-13, SV-BC19-18, SV-BC10-19.
Ø
Cliff is
to propose examples for SV-BC10.
Ø
Dennis to
make a proposal on DSM.
Ø
Karen
will create issues for:
1. Backannotation on interfaces
2. Backannotation on logic type
3. Need a definition of the exact use of interfaces w/o modports
Synthesis tools would compile a module by module.
Ø
Karen
needs to move the following to the enhancement committee:
Scheduling control/delta cycles
Private and public variables for interfaces
Modports as separate entities from interfaces
Ø
Peter
will clarify extern fork/join semantics. In particular:
§
Disabling
calls for joined tasks needs to be clarified
§
Need to
document the behavior for modules that do not define interface
tasks. (SV-BC16)
Ø
Gord will make a
proposal to describe the granularity of error checking on logic types in the
presence of mixed continuous and procedural assignments. (SV-BC18)
Ø
Dave Rich
will make a proposal describing port directions and/or collapsing are possible with
logic type and the associated restrictions. (SV-BC18g)
Ø
Karen
will propose some language indicating that when a logic type has an initializer, all assignments must be procedural. (SV-BC18h)
Ø
Dave will
propose some language indicating that logic types cannot be driven by
primitives that pass strength: MOS switches, etc. (SV-BC19i)
Ø
Johny
will check with the EC as to why they need type use before definition. We
will discuss this in our next meeting. (SV-BC8-3)
Ø
Dave will
develop language to clarify the description of time precision and time scale.
(SV-BC2)
Ø
Peter
will develop language to address issues with time variables and literals.
(SV-BC8-5)
Ø
Steven
will develop language to clarify the meaning of type "matching" in
structural literals. (SV-BC7c)
Ø
Dave will
develop language to clarify the transition of 2-state types to 4-state in
packed unions. (SV-BC8-2b)
Ø
Stu will implement
the global replacement of masked with 4-state and unmasked with 2-state.
(SV-BC8-7)
Ø
Karen
will propose language correcting the standards conversion between shortreal and integer. (SV-BC9-10)
Ø
Gord will propose shortreal equivalents of $bitstoreal
and $realtobits (SV-BC9-10)
Ø
Peter
will propose language for what can and cannot appear in a constant expression.
(SV-BC12)
Ø
Gord will propose
language describing the implicit sensitivity list for always_comb,
noting that always_comb is equivalent to always
<statement> @(sensitivity) (SV-BC21)
Ø
Karen
will develop language for auto-increment. (SV-BC6)