[sv-bc] Re: Moving mantis items to the resolved state

From: Jonathan Bromley <jonathanbromley@ymail.com>
Date: Sun Oct 09 2011 - 03:52:41 PDT

Matt, Neil,

Apologies for the delay - I just missed your previous mail before going
quiet for the weekend.

I've uploaded a new proposal for 1067 in both source and PDF form. I
hope it does what's needed.

cheers
Jonathan Bromley

On 09/10/2011 07:31, Maidment, Matthew R wrote:
> Hi Neil.
>
> I'm waiting on Jonathan Bromley in order to wrap up 1067. We approved it with friendly amendments.
> Need the proposal source in order to put it in a proper state for Champions to review.
>
> Matt
> --
> Matt Maidment
> mmaidmen@ichips.intel.com
>
>
>> -----Original Message-----
>> From: Neil Korpusik [mailto:neil.korpusik@oracle.com]
>> Sent: Tuesday, September 27, 2011 4:40 PM
>> To: Little Scott-B11206; Korchemny, Dmitry; Maidment, Matthew R; Charlie
>> Dawson; Mehdi Mohtashemi
>> Cc: Brad Pierce; Thomas Thatcher; Ghassan Khoory; Rich, Dave; Karen Pieper
>> Subject: Moving mantis items to the resolved state
>>
>> FYI,
>>
>> The following mantis items are currently up for a champions email vote.
>> Please make sure that all of the mantis items that have been approved by
>> your technical committee are placed into the resolved state. This is how I
>> know what is ready for the Champions.
>>
>> 1356 SV-EC Multiple inheritance
>> 2081 SV-BC Not clear enough which kinds of statements are prohibited
>> in
>> always_comb
>> 2547 SV-AC local variable read before write
>> 3015 SV-AC Examples of $fatal have bad arguments
>> 3202 SV-AC Clarify on whether certain system functions are allowed in
>> classes, 'let', and other corner cases
>> 3213 SV-AC Update definition of sampled value
>> 3326 SV-BC LRM in BNF allows parameters declaration under generate,
>> while
>> in generate chapter it is forbidden
>> 2289 SV-BC 6.20.1 should say that generate block and compilation unit-
>> scope
>> parameters are local
>> 2093 SV-AC Checker construct should permit output arguments
>>
>> I know that a few additional mantis items were approved this week. There
>> may be others from previous weeks that have been approved but not moved to
>> the resolved state. Now is the time to take care of this.
>>
>> The technical committees have until this Saturday to complete their work on
>> new proposals. After that, the committees are only allowed to work on
>> feedback from the Champions. The only exception to this is for the sv-cc
>> which has an additional 2 weeks to finish any work that is required due to
>> activity within another committee.
>>
>> There isn't much time left, so I suggest that any work required due to
>> Champion's feedback get done right away. The schedule calls for everything
> >from the technical committees and the Champions to be done by October 27th.
>> The Champions will need some time to review any updates from the technical
>> committees.
>>
>>
>> Neil
>>
>>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Sun Oct 9 03:53:02 2011

This archive was generated by hypermail 2.1.8 : Sun Oct 09 2011 - 03:53:08 PDT