[sv-ac] RE: [sv-sc] 28-04-2008: SV-SC Agenda

Neil-- are you sure this needs to be an SC issue, rather than an AC
issue?

-----Original Message-----
From: Neil.Korpusik@Sun.COM [mailto:Neil.Korpusik@Sun.COM] 
Sent: Friday, April 25, 2008 6:28 PM
To: Seligman, Erik
Cc: sv-sc@eda.org
Subject: Re: [sv-sc] 28-04-2008: SV-SC Agenda

Hi Erik,

Mantis 2370 should be added to the outstanding agenda, even if we don't
get to it on Monday.

Neil




Seligman, Erik wrote:
> *System Verilog Special Committee
> (**_http://www.eda-twiki.org/cgi-bin/view.cgi/P1800/SystemVerilogSpecialCo
> mmittee_**)
> Meeting Agenda, 28-04-2008 *
> 
> The next meeting of the sv-sc will be held on Monday April 28, 
> 9am-11am (PDT).
> 
>           o Toll Free Dial In Number: (866)839-8145
>           o Int'l Access/Caller Paid Dial In Number: (215)446-3660
>           o ACCESS CODE: 9301228
> 
> Agenda:
> 
>          1. Review the patent policy
>          2. Approve the minutes from the April 21, 2008 meeting,
>             available at
>             
> _http://www.eda-twiki.org/cgi-bin/view.cgi/P1800/SvScMeetingMinutes2008042
> 1_
> 
>          3. Review of action items (no major items not covered in rest
>             of agenda, so will skip unless someone has specific
concern)
>          4. Logistics topics
>                       + Meeting time change: swap with SV-AC, so
future
>                         SC meetings on Tues. Need to approve by voice
vote.
>                       + Face-to-face: Confirm for Wed 5/14- Thurs 5/15
>                         in Bay area. Find volunteer hosts, or assign
>                         action item to get venues.
>          5. Technical topics
>                       + Concurrent assertions in procedural code:
review
>                         Dmitry's points (Erik to lead discussion since
>                         Dmitry on vacation), try to converge to
concrete
>                         proposal to be written by following week.
>                       + Checkers as variant modules: Review Gord's
email
>                         concerns, try to converge on documented set of
>                         issues preventing/supporting inlining
semantics.
>                       + Let statements: If time remains, review
concerns
>                         here and attempt to come up with concrete
issue
>                         list.
> 
> 
> 
> --
> 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.