RE: [sv-ac] call to vote on 1769

Hi Lisa,

the proposal says 
"The tasks shall be called outside procedural code and their activation
may be controlled by
conditional generate constructs. It is an error if such a task is called
from within a procedure."

I thought that it is enough. The elaboration may or may not  be
affected, but an error means no simulation. Or am I mistaken?

Thanks,
ed 

> -----Original Message-----
> From: Lisa Piper [mailto:piper@cadence.com] 
> Sent: Monday, January 21, 2008 5:38 PM
> To: Lisa Piper; Eduard Cerny; Korchemny, Dmitry; 
> john.havlicek@freescale.com; sv-ac@eda.org
> Subject: RE: [sv-ac] call to vote on 1769
> 
> Hi Ed,
> 
> I have another question.  What does the tool do if it 
> encounters one of
> these tasks in part of the code that depends on a run-time branch?  I
> assume the tool has to figure out that it can't do it and 
> issue an error
> message. Does this stop the elaboration and simulation?
> 
> Lisa
> 
> -----Original Message-----
> From: Lisa Piper 
> Sent: Monday, January 21, 2008 4:16 PM
> To: 'Eduard Cerny'; Korchemny, Dmitry; john.havlicek@freescale.com;
> sv-ac@eda.org
> Subject: RE: [sv-ac] call to vote on 1769
> 
> I vote no because there are several comments to be addressed.
> 
> I would think it would appear in chapter 20 "I/O system tasks and
> functions". Chapter 21 describes compiler `directives.
> 
> We need to be consistent on what these are called, and that should be
> the title of the section too. I like "elaboration system 
> tasks".  I see
> it referred as "elaboration action task", "elaboration action system
> task", "severity system task", and "elaboration action".  
> There is also
> a typo in which system appears twice "All of the elaboration action
> system system tasks shall....."  I don't like using the word "action"
> because I jumped to the conclusion that there were action blocks
> associated
> 
> "If $elab_fatal is executed then after outputting the message the
> elaboration is aborted. This also means that any remaining elaboration
> action task calls may not be executed."   ("may" should be "shall")
> 
> What the user really needs for debug is not only the file and name of
> where the call is made, but where the constant is set especially if it
> is a constant function call.
> 
> Lisa
> 
> 
> 
> 
> 
> -----Original Message-----
> From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
> Eduard Cerny
> Sent: Monday, January 21, 2008 2:10 PM
> To: Korchemny, Dmitry; john.havlicek@freescale.com; sv-ac@eda.org
> Subject: RE: [sv-ac] call to vote on 1769
> 
> Hi,
> 
> corrected and uploaded, following Dmitry's suggestions.
> 
>  Best regards,
> ed
> 
> 
> > -----Original Message-----
> > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On 
> > Behalf Of Korchemny, Dmitry
> > Sent: Monday, January 21, 2008 3:44 AM
> > To: john.havlicek@freescale.com; sv-ac@eda.org
> > Subject: RE: [sv-ac] call to vote on 1769
> > 
> > I vote yes on 1769 with the following friendly amendments:
> > 
> > * Page 1. "The tasks must be called outside procedural code 
> > ..." -> "...
> > shall be called ..."?
> > 
> > * Page 1. 
> > "If $elab_fatal is executed then after outputting the message the
> > run-time code generation is immediately aborted. This also 
> means that
> > any remaining elaboration action task calls may not be executed.
> > If $elab_error is executed then the message is issued and 
> compilation
> > continues. However, no simulation run-time code is generated.
> > The other two tasks $elab_warning and $elab_info only output 
> > their text
> > message but do not affect the compilation and run-time code 
> > generation."
> > 
> > The terms defined in the LRM are "elaboration" and 
> "simulation". Also
> > from 3.10 it looks like that the "compilation" means the processing
> > before the elaboration.
> > 
> > I would rephrase these statements as:
> > "If $elab_fatal is executed then after outputting the message the
> > elaboration is immediately aborted. This also means that 
> any remaining
> > elaboration action task calls may not be executed.
> > If $elab_error is executed then the message is issued and the
> > elaboration continues. However, no simulation shall be executed.
> > The other two tasks $elab_warning and $elab_info only output 
> > their text
> > message but do not affect the rest of the elaboration and the
> > simulation."
> > 
> > Note also the spacing between these three paragraphs.
> > 
> > * Page 2. First example:
> > 
> > Should be if ((N <= 0) || (N > 8))
> > 
> > Thanks,
> > Dmitry
> > 
> > -----Original Message-----
> > From: owner-sv-ac@server.eda.org 
> > [mailto:owner-sv-ac@server.eda.org] On
> > Behalf Of John Havlicek
> > Sent: Wednesday, January 16, 2008 4:11 AM
> > To: sv-ac@server.eda.org
> > Subject: [sv-ac] call to vote on 1769
> > 
> > Hi Folks:
> > 
> > This is the call to vote on the proposal for Mantis 1769.
> > 
> > The document on Mantis is
> > 
> >    ElaborationTimeUserAssert1769.071204.pdf
> > 
> > Please vote if you are eligible.  See details below.
> > 
> > J.H.
> > 
> > --------------------------------------------------------------
> > ----------
> > ----------
> > Ballot on Mantis 1769
> > 
> > - Called on 2008-01-15, final ballots due by 2008-01-21 T 
> 23:59-08:00.
> > 
> >  v[xxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx-xx] Doron Bustan
> > (Intel)
> >  v[xxxxx--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-x] Eduard Cerny
> > (Synopsys)     
> >  n[----------------------x-xxx---------x-x-xxx-x---x] 
> Surrendra Dudani
> > (Synopsys)
> >  v[xxxxxxxx-xxxxxx-xxxxxxxxx-xx-xxxxx-xxx-xxx-------] Yaniv Fais
> > (Freescale)
> >  t[xxxx--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] John Havlicek
> > (Freescale - Chair)
> >  v[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxrxxxxxxxxxxxxx-xxx] 
> Dmitry Korchemny
> > (Intel - Co-Chair)
> >  v[xxxxx-xxxxxxxxx-xxx-x--xx--xxxxx----------xx-xxxx] Manisha
> > Kulshrestha (Mentor Graphics)
> >  n[------------------------------xxxxx-------x-xx-x-] Jiang 
> > Long (Mentor
> > Graphics)
> >  n[---------x------------x--xxx.....................] Joseph 
> > Lu (Altera)
> >  v[xxxxxxxxxxxxxxxxxxx..............................] Johan 
> Martensson
> > (Jasper)
> >  n[---------------------------x--x-xx--xx-xxxxxxx-x-] Hillel Miller
> > (Freescale)
> >  v[xxxxx-xxxx-xxxxxxxxxxxxxxxxxxx-xxxxxxxx-xxxxxxxxx] Lisa Piper
> > (Cadence)
> >  v[xxxxxx-x-x-xx-xxxxxxx-x-xxxxx-x..................] Erik Seligman
> > (Intel)
> >  n[-------x-x----x--------xxxx-----xxxx-xx----------] Tej 
> > Singh (Mentor
> > Graphics)
> >  v[xxxxxx-x-xxxxxx--xxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxx] Bassam Tabbara
> > (Synopsys)
> >  v[xxxxxxxxx-xxxxxxxxxxxxx-xxxxxxxxxx...............] Tom 
> > Thatcher (Sun
> > Microsystems)
> >    |------------------------------------------------- attendance on
> > 2008-01-15
> >  |--------------------------------------------------- voting 
> > eligibility
> > for this ballot
> > |---------------------------------------------------- email ballots
> > received
> > 
> >         Legend:
> >                 x = attended
> >                 - = missed
> >                 r = represented
> >                 . = not yet a member
> >                 v = valid voter (2 out of last 3 or 3/4 overall)
> >                 n = not a valid voter
> >                 t = chair eligible to vote only to make or 
> break a tie
> > 
> > -- 
> > 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.
> > 
> > 
> > 
> 
> -- 
> 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.