| Number | 167
|
| Category | errata
|
| Synopsis | 2001b, 25.13, 25.31: tf_error and tf_message outside checktf
|
| State | lrmdraft
|
| Class | errata-ptf
|
| Arrival-Date | Oct 20 2002
|
| Originator | Shalom Bresticker <Shalom.Bresticker@motorola.com>
|
| Release | 2001b: 25.13, 25.31
|
| Environment |
|
| Description |
I came across this old mail. ---------- Forwarded message ---------- Date: Thu, 09 Aug 2001 10:41:15 -0400 From: Chris Spear <Chris@Spear.net> Can I get a little more clarification on how tf_error and tf_message work outside of the checktf? I suggest the following addition, based on what VCS does: 25.13 tf_error If tf_error is called from the calltf or misctf application associated with the user-defined system task or function, the following rules shall apply: - The calltf or misctf application will be allowed to complete. - No further events in the model will be processed. - All the misctf applications will be called with reason_finish to allow the user-defined system tasks and functions to close. 25.31 tf_message If tf_message is called from the calltf or misctf application associated with the user-defined system task or function, and the level is ERR_ERROR, ERR_SYSTEM, ERR_INTERNAL, the following rules shall apply: - The calltf or misctf application will be allowed to complete. - No further events in the model will be processed. - All the misctf applications will be called with reason_finish to allow the user-defined system tasks and functions to close. Okay, I am a dinosaur for still using these tasks! /***************************************************************** Chris Spear Verification Specialist .. __o Synopsys, Inc. Email Chris@Spear.net _`\<,_ 154 Crane Meadow Road Phone 508-486-5214 .. (*)/ (*) Marlboro, MA 01752 Fax 508-486-5223 My cogs go to 11 http://chris.spear.net Car 508-254-7223 *****************************************************************/ |
| Fix |
Section 25.13 on tf_error(), add the following paragraph to the end of the section: "When tf_error() is called from a sizetf, calltf, or misctf application, the message shall be reported, but no other action shall be taken." Section 25.31 on tf_message(), add the following paragraph just before the third paragraph, which begins with "The facility and code fields shall be string arguments...": "When tf_message() is called with any severity level from a sizetf, calltf, or misctf application, the message shall be reported, but no other action shall be taken." |
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology