******************************************************************************
********************* IBIS GOLDEN PARSER BUG REPORT FORM *********************
******************************************************************************

INSTRUCTIONS

To report a bug in the IBIS golden parser.  Please fill out the top part
of the following form and send the complete form to info@ibis.org.

A list of reported bugs is maintained at http://ibis.org/bugs/ibischk/ .

******************************************************************************

PARSER VERSION NUMBER: 7.0.2

PLATFORM (SPARC, HP700, PC, etc.): N/A

OS AND VERSION:  N/A

REPORTED BY: Michael Mirmak, Intel Corp.

DATE: November 30, 2021

DESCRIPTION OF BUG:

Some EDA tools expect and issue warnings enforcing that the parameter tree
"root name" of a .ami file must match the first string or "root name" provided
by the associated AMI executable (.dll or .so) file, in its
AMI_Parameters_Out string.  The IBISCHK7 parser, however, does not perform
this check, or even report what the AMI_Parameters_Out tree root name string
is.  As tools do not always provide to the user the AMI_Parameters_Out string
in its "raw" form, detecting a mismatch is almost impossible without access to
the executable source code.

In IBIS 7.0, the structure of the executable AMI_Parameters_Out string is
explicitly stated to follow the structure of the AMI_Parameters_In string,
which is provided.  The name of the AMI_Parameters_Out string tree varies in
the IBIS 7.0 document.  From Section 10.2.3, the "root name" is required and
is implied to be the first string output; this string is also called the "top
level parameter string" and is considered a "parameter group".  Section 10.3 
describes the .ami file structure and calls the first string the "root name".

The IBISCHK parser should be enhanced to report any mismatch between the root
name of an executable and the root name of its associated .ami file.  The
association of the files is established under the .ibs file's [Algorithmic
Model] keyword.

Until and unless a BIRD is issued, the parser's output report should be a note
or caution, rather than a warning or error.

While the .ami file is ASCII text and can be read easily regardless of
operating system, checking for root name mismatch requires passing information
to the AMI executable and therefore will be OS-dependent, similar to checking
for required AMI functions.  


INSERT IBIS FILE DEMONSTRATING THE BUG:

N/A


******************************************************************************
******************** BELOW FOR ADMINISTRATION AND TRACKING *******************
******************************************************************************

BUG NUMBER:  227

SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT]  ENHANCEMENT

PRIORITY: [HIGH, MEDIUM, LOW]                               LOW

STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG]             OPEN

FIXED VERSION:

FIXED DATE:

NOTES ON BUG FIX:
Classified at the August 12, 2022 IBIS Open Forum Teleconference.  The
resolution is to be determined after further discussion.

March 20, 2022 Quality Task Group - We noted that we expect only a minimal
change, as outlined in an upcoming BIRD for Version 7.2.

August 12, 2022 - classified after the related BIRD219.1 was approved on
August 12, 2022.  The minimal check could include a simple AMI_Init vector
for Rx and Tx.  Because the check could take a long time, we may want to
have a flage (TBD) to either turn on this check or to disable it.

March 10, 2023 - Due to some complicated issues raised by the parser developer
and by people in the Quality Task Group, a fix is celayed until further
resolution.  The issues involved a potentially unstable parser, a very long
time to complete, and test vecoters that conflict with executable model
symbol_time. A new IBIS-AMI version with either a new reserved parameter 
for testing root names, or a new function for testing root names have been
suggested.  We would reject a separate flag for turning on or turning off
the test.

******************************************************************************
******************************************************************************