Re: [sv-ac] Draft P1800/D9-preliminary review

Hi Dmitry,

I have read through Clause 16.15 and found no issues.

Tom

On 07/02/09 05:58, Korchemny, Dmitry wrote:
> Hi all,
> 
>  
> 
> It is time to review Draft P1800/D9.
> 
>  
> 
> Each SV-AC member is requested to review the implementation of Mantis 
> items assigned to him/her, and in addition the assigned fragment of the 
> LRM. The review is due by 07/10/2009. Please, send a notification when 
> you are done, with the list of issues found or with the indication that 
> the implementation is correct. If you find an issue with Mantis 
> implementation, please, add a corresponding note to the Mantis with the 
> indication of the actions required from the editor, and move the Mantis 
> to the Editor status. If no issues have been found, keep the Mantis 
> unchanged.
> 
>  
> 
> Mantis list:
> 
> 2661 "Syntax 16-19" is in 
> blue                                                     
>                                                                 Dmitry 
> Korchemny 
> 
> 2660 Add indices to expressions               
>                                                                                 
> Doron Bustan                                   
> 
> 2659 Backward compatibility issue with sequence 
> property                                                          Doron 
> Bustan                                   
> 
> 2658       Default values for untyped formals                         
>                                                                 Dmitry 
> Korchemny 
> 
> 2656 Clarify difference of $global_clock handling in simulation and 
> formal verification Tom Thatcher                                        
> 
> 2652 Future value functions need clarification                    
>                                                 
> Erik_Seligman                     
> 
> 2650 Ambiguity in a sequence repetition [*0] definition                 
>                                 Erik_Seligman                     
> 
> 2612       `true should have a backtick in a sequence 
> example                                                        Dmitry 
> Korchemny 
> 
> 2541 syntax errors - missing 
> parenthesis                                        
>                                                        Lisa 
> Piper            
> 
> 2516 Another contradiction of existing text with 2398 needs to be 
> fixed                                 Erik_Seligman                     
> 
> 2486 Scope of Annex F definition of "specify" is not 
> clear.                                                             
> john_havlicek                     
> 
> 2478       Clock flow subclause is not consistent with multiclocked 
> property definition      Dmitry Korchemny
> 
>  
> 
> Fragments:
> 
> Clause 3 (relevant parts) – Tapan
> 
> Clause 15 (relevant parts) – Manisha
> 
> Clause 16
> 
> Beginning – 16.8 (including) Ed
> 
>                 16.9 Ben
> 
>                 16.10 – 16.12 (including), 16.17 – Manisha
> 
>                 16.13 – Doron
> 
>                 16.14 – Lisa
> 
>                 16.15 – Tom
> 
>                 16.16 – 16.18 (including)  Dmitry
> 
> Clause 17 – Erik
> 
> Clause 20 (relevant parts) - Manisha
> 
> Clause 37 (relevant parts) – Bassam
> 
> Clause 39 – Bassam
> 
> Annex A – Tapan
> 
> Annex B – Tapan
> 
> Annex C – Tapan
> 
> Annex F – John
> 
> Annex N – Lisa
> 
>  
> 
> Please, notify me if you are unable to review the assigned 
> fragments/Mantis items.
> 
>  
> 
> Thanks,
> 
> Dmitry
> 
> ---------------------------------------------------------------------
> 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* <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.