******************************************************************************
********************* 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 ibis-bug@eda.org.

A list of reported bugs will be maintained on eda.org.

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

PARSER VERSION NUMBER: 5.1.4

PLATFORM (SPARC, HP700, PC, etc.): PC

OS AND VERSION: Windows 7

REPORTED BY: Mike LaBonte, SiSoft; Bob Ross, Teraspeed Consulting Group

DATE: April 23, 2014

DESCRIPTION OF BUG:

Suppress Repeated AMI File Checking.

IBISCHK checks .ami files each time they are encountered on the Executable
lines in a .ibs file. There is no need to check any .ami file twice.

The test case consists of

  bug154.ibs   (check with ibischk5 -numbered bug154.ibs)
  bug154a.ami  (an AMI_Version "5.1" file)
  bug154.dll   (a meaningless dummy file)

Run ibischk5 bug154.ibs. Repeated checking of bug154a.ami is reported.
The repeated bug154a.ami check shown below should be suppressed.

IBISCHK5 V5.1.4

Checking bug154.ibs for IBIS 5.1 Compatibility...


Checking BUG154a.ami for IBIS 5.1 Compatibility...


Checking BUG154a.ami for IBIS 5.1 Compatibility...

Errors  : 0

File Passed


-------

INSERT IBIS FILE DEMONSTRATING THE BUG:

Three files are included:

----------
bug154.ibs
----------

|****************************************************************
[IBIS Ver]   5.1   | DUMMY IBIS FILE TO SHOW AMI VERSION PROBLEM
[File Name]  bug154.ibs
[File Rev]   0.1
[Date]       April 17, 2014
|
[Component]    BUG154
[Manufacturer] Test File
|
[Package]
R_pkg   0.0    NA    NA    
L_pkg   0.0    NA    NA    
C_pkg   0.0    NA    NA    
|
[Pin]    signal_name     model_name      R_pin  L_pin  C_pin
1p       RxP             Rxa             NA     NA     NA    
2p       RxP             Rxb             NA     NA     NA    
|
|****************************************************************
|****************************************************************
[Model]     Rxa  | Version "5.1" .ami file
Model_type  Input
|
C_comp 0.00p 0.00p 0.00p
Vinh = 0.55
Vinl = 0.45
[Voltage Range]      1.2   1.14  1.26
|
[Algorithmic Model] 
Executable   Windows_VisualStudio_32   BUG154.dll  BUG154a.ami
[End Algorithmic Model]
|
|****************************************************************
[Model]     Rxb  | Version "5.1" .ami file
Model_type  Input
|
C_comp 0.00p 0.00p 0.00p
Vinh = 0.55
Vinl = 0.45
[Voltage Range]      1.2   1.14  1.26
|
[Algorithmic Model] 
Executable   Windows_VisualStudio_32   BUG154.dll  BUG154a.ami
[End Algorithmic Model]
|
|****************************************************************
[End]

-----------
bug154a.ami
-----------

 (BUG154a  |  VERSION "5.1", NO Use_Init_Output
    (Reserved_Parameters
       (AMI_Version
          (Usage Info)
          (Type String)
          (Value "5.1")
      )
       (Init_Returns_Impulse
          (Usage Info)
          (Type Boolean)
          (Value True)
      )
       (GetWave_Exists
          (Usage Info)
          (Type Boolean)
          (Value True)
      )
   )
 )


----------
bug154.dll
----------

DUMMY CONTENT
END



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

BUG NUMBER:  154

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

PRIORITY: [HIGH, MEDIUM, LOW]                               LOW

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

FIXED VERSION:  6.0.0

FIXED DATE:     June 20, 2014

NOTES ON BUG FIX:

Classified at the April 25, 2014 IBIS Teleconference meeting.  To be fixed
in a future release.

June 16, 2014 - the BUG153 test case is also used for BUG15.4

Approved at the June 20, 2014 IBIS Teleconference Meeting.

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