****************************************************************************** ********************* 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.0 PLATFORM (SPARC, HP700, PC, etc.): IA64 OS AND VERSION: Microsoft Windows* 7 REPORTED BY: Walter Katz, Signal Integrity Software; Bob Ross, Teraspeed Consulting Group; and Michael Mirmak, Intel DATE: September 28, 2012 DESCRIPTION OF BUG: The enclosed .ami file will produce the following incorrect error when analyzed using IBISCHK5, Version 5.1.0: ERROR - Failing_Integer_Default_0: Default value (0) is not in Format List ERROR - Failing_Float_Default_0.0: Default value (0.0) is not in Format List ERROR - Failing_Float_Default_0.0_last: Default value (0.0) is not in Format List The lines causing the errors all use a value of 0 or 0.0 (depending on Type) as the Default entry, and all include this Default in the associated List. The IBIS 5.1 specification clearly states that, while Default is optional for List: "... if Default is specified, shall be a member of the set of allowed values of the parameter." In each case, the Default value of 0 or 0.0 is clearly a member of the List, but is not being identified correctly as such by the parser. Other Default values do not have this effect. INSERT IBIS FILE DEMONSTRATING THE BUG: (Bug138 (Description "SERDES receiver model provided by SiSoft") (Reserved_Parameters (AMI_Version (Value "5.1") (Type String) (Usage Info)) (Ignore_Bits (Usage Info) (Type Integer) (Value 100000) (Description "The output may take a while to converge.")) (Max_Init_Aggressors (Usage Info) (Type Integer) (Value 25) (Description "Number of aggressors is actually unlimited.")) (Init_Returns_Impulse (Usage Info) (Type Boolean) (Value True) (Description "Both impulse and parameters_out returned.")) (GetWave_Exists (Usage Info) (Type Boolean) (Value True) (Description "GetWave is well and truly provided in the module.")) (Rx_Receiver_Sensitivity (Usage Info)(Value 0.050)(Type Float) (Description "The sensitivity for the receiver.")) ) | End Reserved_Parameters (Model_Specific (Passing_Integer_Default_1 (List 0 1)(Usage In)(Type Integer)(Default 1) (Description "Adaptive equalization control")) (Failing_Integer_Default_0 (List 0 1)(Usage In)(Type Integer)(Default 0) (Description "Adaptive equalization control")) (Passing_Integer_Default_1of2 (List 1 2)(Usage In)(Type Integer)(Default 1) (Description "Adaptive equalization control")) (Passing_Integer_Default_2of2 (List 1 2)(Usage In)(Type Integer)(Default 2) (Description "Adaptive equalization control")) (Passing_Float_0 (List 0.0 1.0)(Usage In)(Type Float)(Default 1.0) (Description "Adaptive equalization control")) (Failing_Float_Default_0.0 (List 0.0 1.0)(Usage In)(Type Float)(Default 0.0) (Description "Adaptive equalization control")) (Passing_Float_Default_1.0 (List 1.0 0.0)(Usage In)(Type Float)(Default 1.0) (Description "Adaptive equalization control")) (Failing_Float_Default_0.0_last (List 1.0 0.0)(Usage In)(Type Float)(Default 0.0) (Description "Adaptive equalization control")) (Passing_Float_Default_1.0of2 (List 1.0 2.0)(Usage In)(Type Float)(Default 1.0) (Description "Adaptive equalization control")) (Passing_Float_Default_2.0of2 (List 1.0 2.0)(Usage In)(Type Float)(Default 2.0) (Description "Adaptive equalization control")) ) | End Model_Specific ) ****************************************************************************** ******************** BELOW FOR ADMINISTRATION AND TRACKING ******************* ****************************************************************************** BUG NUMBER: 138 SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] SEVERE PRIORITY: [HIGH, MEDIUM, LOW] HIGH STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] CLOSED FIXED VERSION: 5.1.2 FIXED DATE: October 5, 2012 NOTES ON BUG FIX: Fixed in Version 5.1.2. ****************************************************************************** ******************************************************************************