RE: [sv-ec] Provide your SV-EC prioritized list for next LRM (PAR) [Due: Feb 3. 2010]

Hi Tom,
It would be good to see what you have available, as I will combine all
inputs for sv-ec as well.
We will of course go over all inputs at the time of Face-to-Face.
thanks,
- Mehdi

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Alsop, Thomas R
Sent: Thursday, February 04, 2010 11:27 AM
To: Mehdi Mohtashemi
Cc: sv-ec@eda.org
Subject: RE: [sv-ec] Provide your SV-EC prioritized list for next LRM (PAR) [Due: Feb 3. 2010]

Hi Mehdi,

I will be collecting sv-ec requirements for Intel. Matt Maidment and I are working on this and as Matt is leading the sv-bc team, he will be presenting at the PAR meeting Friday after DVCon. While I do have a small list, we won't have a full list for another two weeks. Do you want me to give you what I have now or can this wait two weeks before passing on to you, or just have Matt present them for Intel?

Thanks, -Tom

________________________________
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Mehdi Mohtashemi
Sent: Wednesday, February 03, 2010 4:38 PM
To: Mirek Forczek
Cc: sv-ec@eda.org
Subject: RE: [sv-ec] Provide your SV-EC prioritized list for next LRM (PAR) [Due: Feb 3. 2010]

Thanks Mirek for your input. I will compile a list for the p1800WG meeting
based on all inputs.
Regards,
- Mehdi

From: Mirek Forczek [mailto:Mirek.Forczek@aldec.com.pl]
Sent: Wednesday, February 03, 2010 7:47 AM
To: Mehdi Mohtashemi
Cc: sv-ec@eda.org
Subject: Re: [sv-ec] Provide your SV-EC prioritized list for next LRM (PAR) [Due: Feb 3. 2010]

Hello Mehdi,

I would like to provide an input.
There are two existing scopes in language to which I would give priority for possible improvements.

scope 1: classes

(critical clarifications, if left unresolved may lead to the tools incompatiblity issues)
- (0002470) The order of initialization of class properties initialized in the declaration vs. contructor calls should be clearly defined.
- (0001511) $typename() and parameterized classes (22.2)
- (0001584) problems with default arguments in virtual methods

(important syntax/semantics enhancements/closures)
- (0002487) Syntax for specifing an object type when creating a object - syntax proposal : b = C::new; or b = new C;
- (0002349) CONST: LRM should add constant method/function/task and introduce 'const pointer' and 'pointer const' functionality
- (0002735) Ballot Comment #48: Chaining of method calls
- (0002972) add class constructor/method, task/function overloading
- (0002350) Local, protected modifiers allowed for nested class declaration

(supplemental issues)
- (0002950) virtual method prototype matching
- (0002787) reference via scope operator to parametrized superclass item
- (0002080) "::" is ambiguous in parameterized classes

scope 2: random constraints

(recently filed)
- (0002967) define explicitly legal set of data types for randomize variables list
- (0002968) allow constraint reference at constraint expression
- (0002969) allow data members references in in-line random variable control (8.11)
- (0002970) allow hierarchical references in randomization of scope variables-std::randomize() (18.12)
- (0002971) allow scope constraint definition (in module/interface/program/checker)

(already found in database)
- (0002936) srandom, set_randstate restrictions
- (0002522) Constraint ordering with function calls
- (0001516) arguments to randomize calls

Regards,
Mirek Forczek

On 2010-02-03 11:08, Mehdi Mohtashemi wrote:

Send in your inputs by end of today, Wednesday February 3, 2010.

Many of you may have seen correspondence from p1800-WG,

 http://www.eda-stds.org/sv-ieee1800/hm/0956.html [sent by Neil]

and other sub-comittees, such as sv-bc requesting members to

provide their inputs.

[I am using the template sent by Brad in his email to sv-bc].

For the PAR for next LRM standard work, Neil and I are gathering

requirements from members. The PAR will be discussed

at next p1800WG meeting. We will present the prioritized list to the

group.

You can refer to the database Mantis items for SV-EC:

 http://tinyurl.com/ybylbso

and use this for your reference. Note that the sv-ec items are

generally targetted for the testbench/verification subset.

There are many subscribers to the sv-ec email alias, so I would expect

members will pay attention and provide their inputs for our next step.

Please use the following as the guideline:

- Send your inputs by end of Feb 3 2010.

- Include the mantis item(s) and rank them. Provide us with a prioritized

  list.

- If there is an issue that is not part of mantis database, add it to the

  system under sv-ec, or send it to us we can add it.

- Provide a meaningful background and reason for the requested enhancement.

Please send us your inputs. thanks,

Mehdi

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.