[ibis-macro] Re: Error reporting in IBIS-AMI

  • From: "Walter Katz" <wkatz@xxxxxxxxxx>
  • To: <Arpad_Muranyi@xxxxxxxxxx>, "'IBIS-ATM'" <ibis-macro@xxxxxxxxxxxxx>
  • Date: Tue, 27 Mar 2012 17:15:57 -0400 (EDT)

All,

 

We could implement the following (not negative return codes are
problematic on some OS):

 

| 1 for success 

| 0 for failure

|2 for CANNOT_LOAD_LIBRARY

|3 for CANNOT_FIND_FUNCTION

 

#define CANNOT_LOAD_LIBRARY 2

#define CANNOT_FIND_FUNCTION 3

 

Since DLL does not read AMI FILE the following do not make sense

#define CANNOT_LOAD_AMI_FILE 

#define CANNOT_PARSE_AMI_FILE 

 

Walter

 

From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, March 27, 2012 5:06 PM
To: IBIS-ATM (ibis-macro@xxxxxxxxxxxxx)
Subject: [ibis-macro] Re: Error reporting in IBIS-AMI

 

Unfortunately the spec currently says that:

 

| 3.1.3 Return Value 

| 

| 1 for success 

| 0 for failure

 

Which pretty much kill the possibilities to implement

an indication for what the error is.

 

Thanks,

 

Arpad

======================================================

 

 

From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Tuesday, March 27, 2012 3:11 PM
To: IBIS-ATM (ibis-macro@xxxxxxxxxxxxx)
Subject: [ibis-macro] Error reporting in IBIS-AMI

 

A colleague asked the following question, which he asked to be sent to
this list for discussion.  Apologies if this has already been discussed.

 

If an IBIS-AMI model returns an (assigned) error (e.g. -4), what does it
mean to the EDA tool?

 

Having standardized error handling categories described in the
specification, to defines the return states, would be useful. This would
also give the tool user some way of debugging easy errors without
requiring contacting the original model authors.

 

e.g., the specification might suggest the following assignments which
would be implemented in the EDA tool:

.

#define CANNOT_LOAD_LIBRARY -1

#define CANNOT_FIND_FUNCTION -2

#define CANNOT_LOAD_AMI_FILE -3

#define CANNOT_PARSE_AMI_FILE -4

#define ..

.

#define UNKNOWN -99

 

The EDA tool could then either perform some intelligent checks (for
example, wider searches for the file) or the user could double-check that
the files are in the right location, the right OS/architecture is being
used for simulation, etc.

 

-          MM

Other related posts: