[sv-ec] sv-ec mantis item spreadsheet for PAR discussion

I have attached a .xls spreadsheet that shows the mantis items for sv-ec.

Here is also the list we have received from users (appended),

we will review in the meeting today.

Mehdi

Gordon

1527 - can class methods be constant functions

1685 - parameters and strings

2707 - string concatenation

2080 - "::" in parameterized classes (addressed already)

2845 - virtual interface type equivalence

1441/1706 - virtual interfaces and sensitivities

3012 - clocking block clarifications

2470 - further class initialization clarifications

2549 - unparenthesized calls

2554 - class base pointer clarifications

2286 - local/protected access with inline constraints

2073 - min/max minor clarification

0237 - wait/fork clarification

1363/1349 - fork/join clarifications

Mirek Forczek Aldec

scope 1: classes

(critical clarifications, if left unresolved may lead to the tools incompatiblity issues)

Enhancement(2470) The order of initialization of class properties initialized in the declaration vs. contructor calls should be clearly defined.

Errata (1511) $typename() and parameterized classes (22.2)

Errata (1584) problems with default arguments in virtual methods

(important syntax/semantics enhancements/closures)

Enhancements

(2487) Syntax for specifing an object type when creating a object - syntax proposal : b = C::new; or b = new C;

(2349) CONST: LRM should add constant method/function/task and introduce 'const pointer' and 'pointer const' functionality

(2735) Ballot Comment #48: Chaining of method calls

(2972) add class constructor/method, task/function overloading

(2350) Local, protected modifiers allowed for nested class declaration

Errata - (2950) virtual method prototype matching

Clarifications - (2787) reference via scope operator to parametrized superclass item

Errata (2080) "::" is ambiguous in parameterized classes

scope 2: random constraints

(recently filed)

Clarifications(2967) define explicitly legal set of data types for randomize variables list

Enhancement (2968) allow constraint reference at constraint expression

Enhancement(2969) allow data members references in in-line random variable control (8.11)

Enhancement(2970) allow hierarchical references in randomization of scope variables-std::randomize() (18.12)

Enhancement(2971) allow scope constraint definition (in module/interface/program/checker)

(already found in database)

Errata(2936) srandom, set_randstate restrictions

Errata(2522) Constraint ordering with function calls

Errata(1516) arguments to randomize calls

Dave Rich Mentor

Enhancement 1356: Multiple inheritance

Enhancement 2112: Remove restrictions on NBA assigments to class members

Errata 2954: covergroup clause is unclear on degenerate open value ranges

Enhancement 2117: Allow extending of covergroups in classes

Errata 2055: coverage bin distribution is not even

Enhancement 2506: Non-trivial coverage space shapes and joint conditions are difficult to specify with covergroups

Srinivasan svenka3@gmail.com

- Ability of "deep_copy, deep_compare" from E/Vera (object_copy..)

- FCOV: cross-of-cross, hierarchical cross

- AOP - my TOP priority REQUEST.

- Variable part/bit select

Cliff Cummings

(1) AOP when-inheritance (slide 31)

(2) Allow extension of enumerated types (slide 31)

(3) Allow reuse of enumerated names (slide 31)

Allow extension of covergroups (slide 31)

Daniel Schostak ARM

(1) Ability to derive class from multiple parents (point 1 on slide 6, preference for java style multiple "interface" inheritance)

(2) Pointer copying for arrays and functions (points 1 and 2 on slide 4)

(3) Expressive enhancements (slide 5 including allowing chaining function invocations and use of new outside of declaration contexts)

(4) Ambiguity resolution (see slide 10 for examples of parts of the Standard that have been interpreted differently by different simulators)

(5) Extend support for generic programming (in particular point 3 on slide 4 about passing expressions to const ref arguments and point 3 on slide 6 about only parsing what is used, but would also include parameterized functions and variable number of function arguments as mentioned by others)

(6) Explicit support for cut points / stop ats in model checking (point 1 on slide 9)

(7) Simplify cross hierarchical references (various points on slide 7)

From Steven Sharp Cadence

I don't think there is a Mantis item for it, but we should consider adding "ref static" arguments which can only be passed references to static variables, but can then be referenced inside fork..join_none/ join_any blocks. This would allow the creation of subprocesses that wait on signals in the design.

It might also be possible to extend this to allow ref variables and class members, instead of just arguments, to provide a more general pointer capability.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.