Re: [Fwd: Minutes of Verilog-AMS meeting - 31 Jan 2008]

Sri -
I don't see any mention in the minutes of the $random and $rdist
functions being reviewed.  In particular, the whole business of
the type_string argument is poorly explained in the current LRM.
(What is the default behavior, if no type_string is given?  What
does it mean "each instance that references this value"?)

It also appears that the text that was added to allow the seed
argument to be a parameter (which is needed if you want to use
$rdist_ to set a parameter, eg the threshold voltage or oxide
thickness) may violate P1800's sematics for $random.

-Geoffrey



Sri Chandra wrote:
> 
> Hi all,
> 
> Resending the minutes of last AMS meeting. Sent it out on Friday night 
> with 2 attachments (impact sections for chapters 8 & 9) which probably 
> was the problem. Shouldn't have been as the size wasn't very big. 
> Removed the attachment and resending the minutes.
> 
> cheers,
> Sri
> 
> -------- Original Message --------
> Subject: Minutes of Verilog-AMS meeting - 31 Jan 2008
> Date: Sat, 02 Feb 2008 02:46:01 +0530
> From: Sri Chandra <sri.chandra@freescale.com>
> Organization: Freescale Semiconductor Inc.
> To: Verilog-AMS LRM Committee <verilog-ams@eda.org>
> 
> 
> Attendees:
> * Patrick O'Halloran - Tiburon
> * Martin O'Leary, Cadence
> * Marek Mierzwinski, Tiburon
> * Sri Chandra, Freescale
> * Boris Troyanovsky, Tiburon
> 
> Chapter discussed:
>   - Clause 7.4 onwards (Mixed signal)
>   - Clause 8 (Scheduling semantics)
>   - Clause 9 (System tasks and functions)
> 
> Clause 7, Mixed signal
>    - (pg 166) problem with section numbering (0.0.0.2) for "Coercing
> discipling resolution" clause.
>    - (pg 169, clause 7.7) Clarification: Not sure about the editors note
> on this clause. All the BNF syntax items seem to be correct.
>    - (clause 7.10 and 7.11) Both these clauses should be deleted as they
> have already been moved to Clause 9 - System tasks and functions.
> 
> Clause 8, Scheduling semantics
>    - (pg 193, clause 8.3.1) The cross-reference needs to be updated from
> 3.4.3.2 to 3.6.3.2
>    - (pg 193) remove "Note" at the bottom of the page. Refer impact
> section attached.
>    - Need to ensure that all the points in the impact section
> (merged_sync_impact_v3.pdf) attached are covered for draft3.
> 
> Clause 9, System tasks and functions
>    - (pg 209) Change title to Table 9-8 to "Conversion system functions"
>    - (pg 212) delete clause 9.2.1 and merge the tables 9-18 and 9-19
> under clause 9.2
>    - (pg 213, clause 9.3) cross-references REF9.2 refers to 8.2 and
> REF9.3 refers to 8.3
>    - (pg 217, clause 9.5.1.1) The correct cross-reference is Clause 8
>    - (pg 218, clause 9.5.2) add $fdebug to file_output_task_name in the
> BNF snippet. Also update the paragraph following the BNF to refer to
> "five" formatted display tasks instead of "four". No impact on BNF as we
> don't explicitly list all system tasks, similar to 1364.
>    - (pg 223, clause 9.7.3) AI on Martin: Martin will send the body of
> this clause which is missing.
>    - (pg 227, clause 9.14) The correct cross-references in this clause
> should be 4.2 and table 4-17.
>    - (pg 234, clause 9.18) remove note. the examples are already
> included in this clause.
>    - (pg 236, clause 9.19) remove note.
>    - Need to ensure that all the points in the impact section
> (merged_systask_impact.pdf) attached are covered for draft3.
> 
> 
> Next review on 7th Feb 2008: Chapter 10 onwards.
> 
> cheers,
> Sri

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.