RE: [sv-bc] BC Issues that must be addressed for 1800-2008

From: Bresticker, Shalom <shalom.bresticker_at_.....>
Date: Tue Oct 02 2007 - 23:30:14 PDT
Another I think we should try to address is the joint SV-BC/SV-AC $
issue, which is Manti 966, 1350, 1982.

Shalom


> -----Original Message-----
> From: owner-sv-bc@server.eda.org 
> [mailto:owner-sv-bc@server.eda.org] On Behalf Of Maidment, Matthew R
> Sent: Tuesday, October 02, 2007 7:18 PM
> To: sv-bc@server.eda.org
> Subject: RE: [sv-bc] BC Issues that must be addressed for 1800-2008
> 
> Per the October 1 meeting, the deadline for identifying 
> issues that must be addressed by feature freeze is October 15.
> 
> Matt
> --
> Matt Maidment
> mmaidmen@ichips.intel.com
>   
> 
> >-----Original Message-----
> >From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of 
> >Maidment, Matthew R
> >Sent: Thursday, September 27, 2007 9:42 AM
> >To: sv-bc@eda.org
> >Subject: [sv-bc] BC Issues that must be addressed for 1800-2008
> >
> >We need to identify the remaining issues that must be addressed for 
> >1800-2008.
> >Neil sent this list:
> >
> >  JEITA-related
> >   1825 - 3.10 Elaboration statement to be revised   - closed (won't
> >fix)
> >   1831 - 22.2.2.2 Module port headers clarification - closed (no 
> >change
> >req)
> >   1826 - Annex B Add keyword list by LRM version             
> >- Assigned
> >   1827 - 20.3.1 Update the OS Reference                      - new
> >   1828 - 9.2.2.3, 9.2.2.4 should/can and mandatory statements- new
> >   1829 - 6.8 usually logic [31:0] would be little endian.    - new
> >   1832 - path rule/scope rule is not clearly described here. - new
> >
> >  1800-2005 Ballot Items
> >   675  - Packed unions shall not be restricted to equal 
> length items - 
> >feedback
> >   676  - Add support of unconstraint arrays                  
> >- feedback
> >   678  - Variables shall be allowed for slicing vectors.     
> >- feedback
> >   697  - file IO tasks and new SV data types                 
> >- feedback
> >   677  - unique/priority violation should be errors          
> >- assigned
> >
> >   698  - No Definition of Error and Warning                  
> >- assigned
> >
> >
> >
> >Please take the time to look into Mantis and follow-up to 
> this thread 
> >with your list.  If you have some issues that have not been filed, 
> >please do so ASAP.  We will soon limit the scope of our work to a 
> >limited number of Mantis items in order to wrap up work on 
> 1800-2008 .
> >
> >Matt
> >--
> >Matt Maidment
> >mmaidmen@ichips.intel.com
> > 
> >
> >--
> >This message has been scanned for viruses and dangerous content by 
> >MailScanner, and is believed to be clean.
> >
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Oct 2 23:30:38 2007

This archive was generated by hypermail 2.1.8 : Tue Oct 02 2007 - 23:30:46 PDT