| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 476
|
| Category | enhancement
|
| Synopsis | Standard reporting mechanism for functional errors/warnings, etc.
|
| State | open
|
| Class | enhancement
|
| Arrival-Date | Sep 16 2003
|
| Originator | Adam Krolnik
|
| Release | 2001b
|
| Environment |
|
| Description |
There is no standard way to write an error message, or a warning message from verification code (or RTL code too.) Thus everyone writes their own with their own format, etc. There should be a mechanism that allows one to: Produce an error message composed of: a user defined message, with varied arguments printed the simulation time the hierarchical name of the code producing the message. the file and line number of the code location. Produce a warning message composed of the same information. Produce an informative message composed of the same information. Produce a fatal message composed of the same information and finish the simulation. A method to count error messages and finish or stop or do nothing to the simulation. A method to disable warning messages from printing. A method to specify the number of error messages before finishing or stopping. |
| Fix |
|
| Audit-Trail |
|
| Unformatted |
|
Hosted by Boyd Technology