Hi Lisa, I would be good if you can modify the language which implies that assertion action control tasks only apply to concurrent assertions. They apply to concurrent and immediate assertions (in fact immediate assertion section mentions them). The proposal says that "While immediate assume and immediate assert statements can be included in automatic tasks, functions, and blocks, and in fork...join, fork...join_any, or fork...join_none blocks, they cannot be controlled by system tasks, action block controls, or VPI.". What is the reason that these assertions are not controllable by system tasks etc ? I thought a hierarchical path still exists to these assertions even if they are in automatic tasks to be able to control them. Thanks. Manisha -----Original Message----- From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Behalf Of Thomas Thatcher Sent: Wednesday, January 09, 2008 6:08 AM To: Lisa Piper Cc: sv-ac@server.eda.org Subject: Re: [sv-ac] RE: 2091 where can assertions be Hi Lisa, I have reviewed the proposal for 2091. It looks good to me. Tom Lisa Piper wrote: > Hi Tom, > > I have created the proposal now. It is attached and on Mantis. > > Manisha and Ed, > > I would appreciate your reviews as well since I noticed an issue with > assertion action controls and because it touches the text of 1729 (but > don't worry Ed - no changes for 1729!) > > Lisa > > > -----Original Message----- > From: Thomas.Thatcher@Sun.COM [mailto:Thomas.Thatcher@Sun.COM] > Sent: Tuesday, December 18, 2007 8:27 PM > To: Lisa Piper > Cc: sv-ac@eda.org > Subject: Re: 2091 > > Hi Lisa, > > I have looked at your proposal, and the concept looks OK. At the > moment, I can't think of any additional restrictions I would add to the > proposal. > > Tom > > > Lisa Piper wrote: >> Hi Tom, >> >> I have uploaded the "proposal" to Mantis. It is not really a proposal > >> yet. I would like to get agreement on the content and then I'll figure > >> out where to put it. >> >> <<2091_071204_lp.doc>> >> >> Lisa >> > -- 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.Received on Tue Jan 8 22:15:25 2008
This archive was generated by hypermail 2.1.8 : Tue Jan 08 2008 - 22:15:55 PST