| Number | 367
|
| Category | errata
|
| Synopsis | 27.32 Cancelling event does not say what happens to handle
|
| State | lrmdraft
|
| Class | errata-ptf
|
| Arrival-Date | Jun 24 2003
|
| Originator | Charles Dawson
|
| Release | 2001b: 27.32
|
| Environment |
|
| Description |
The paragraph that describes how to cancel an event does not say specifically whether the handle to the event is considered freed after the call to vpi_put_value(). The other possibility is that the application must explicitly call vpi_free_object() on the handle. |
| Fix |
27.32, third full paragraph, which begins: "The handle to the event can be cancelled...", Replace the first sentence with: "A scheduled event can be canceled by calling vpi_put_value() with obj set to the vpiSchedEvent handle and flags set to vpiCancelEvent." Where "obj" and "flags" are italicized. Add to end of the paragraph: "Cancelling an event shall also free the handle to that event." |
| Audit-Trail |
From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: ptf-bugs@boyd.com Cc: Subject: Re: errata/367: 27.32 Cancelling event does not say what happens to handle Date: Thu, 26 Jun 2003 17:02:27 +0300 That same paragraph begins, "The handle to the event can be cancelled by calling vpi_put_value() with the flag set to vpiCancelEvent." Would it be better to say, "An event can be cancelled by ..."? > The paragraph that describes how to cancel an event does not > say specifically whether the handle to the event is > considered freed after the call to vpi_put_value(). The > other possibility is that the application must explicitly > call vpi_free_object() on the handle. Shalom From: Charles Dawson <chas@cadence.com> To: ptf-bugs@boyd.com Cc: Subject: Re: errata/367: 27.32 Cancelling event does not say what happens to handle Date: Thu, 26 Jun 2003 10:32:59 -0400 The problem is not with the cancelling of the event. That is pretty clear. The problem is with the handle to the event itself. Does cancelling the event invalidate the handle (free it)? Or do you need to tell the simulator that the application is done with this handle, via a call to vpi_free_object(). -Chas Shalom Bresticker wrote: > > Precedence: bulk > > The following reply was made to PR errata/367; it has been noted by GNATS. > > From: Shalom Bresticker <Shalom.Bresticker@motorola.com> > To: ptf-bugs@boyd.com > Cc: > Subject: Re: errata/367: 27.32 Cancelling event does not say what happens to > handle > Date: Thu, 26 Jun 2003 17:02:27 +0300 > > That same paragraph begins, > "The handle to the event can be cancelled by calling vpi_put_value() with the > flag set to vpiCancelEvent." > > Would it be better to say, "An event can be cancelled by ..."? > > > > The paragraph that describes how to cancel an event does not > > say specifically whether the handle to the event is > > considered freed after the call to vpi_put_value(). The > > other possibility is that the application must explicitly > > call vpi_free_object() on the handle. > > Shalom > -- Charles Dawson Senior Engineering Manager NC-Verilog Team Cadence Design Systems, Inc. 270 Billerica Road Chelmsford, MA 01824 (978) 262 - 6273 chas@cadence.com Fix replaced by etf@boyd.com on Mon Dec 15 12:27:31 2003 27.32, third full paragraph, which begins: "The handle to the event can be cancelled...", Replace the first sentence with: "A scheduled event can be canceled by calling vpi_put_value() with obj set to the vpiSchedEvent handle and flags set to vpiCancelEvent." Where "obj" and "flags" are italicized. Add to end of the paragraph: "Cancelling an event shall also free the handle to that event." |
| Unformatted |
|
Hosted by Boyd Technology