****************************************************************************** ********************* 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.0.0 PLATFORM (SPARC, HP700, PC, etc.): PC OS AND VERSION: Windows XP - Service Pack 3 REPORTED BY: Todd Westerhoff, SiSoft DATE: Dec 8, 2009 DESCRIPTION OF BUG: The Model_Specific parameters in the example .ami file are flagged by the parser ... the parameters use type "String" and generate the following errors: IBISCHK5 V5.0.0 Checking bug109.ami for IBIS 5.0 Compatibility... ERROR - Value: Illegal Format for my_control_1. Expected 1 number(s) ERROR - Corner: Illegal Format for my_control_2. Expected 3 number(s) Errors : 2 File Failed It seems as though the parser expects parameters to only be numeric values. Specifically, the failure is with the "Type String" and "Type Boolean", but the specification states that all Types are allowed as Value arguments A more rigorous cross-checking of the Type argument and the actual data arguments (currently not done) is a possible consideration, but is not officially included in BUG109 INSERT IBIS FILE DEMONSTRATING THE BUG: bug109.ami -------- (bug109 (Reserved_Parameters (Ignore_Bits (Usage Info) (Type Integer) (Default 10000) (Description "Recommended time finish initialization.")) (Max_Init_Aggressors (Usage Info) (Type Integer) (Default 0) (Description "No crosstalk processing in this model")) (Init_Returns_Impulse (Usage Info) (Type Boolean) (Default False) (Description "Init call does not modify impulse response.")) (GetWave_Exists (Usage Info) (Type Boolean) (Default True) (Description "GetWave is provided in the module.")) (Use_Init_Output (Usage Info) (Type Boolean) (Default False) (Description "Not applicable - init doesn't return modified impulse response.")) (Rx_Receiver_Sensitivity (Usage Info)(Type Float)(Format Value 0.050)(Default 0.050) (Description "Receiver sensitivity.")) ) | End Reserved_Parameters (Model_Specific (my_control_1 (Usage In)(Format Value "String Data")(Type String) (Default "String Data")(Description "Text string that has fixed value") ) (my_control_2 (Usage In)(Format Corner "Normal Corner Data" "Min Corner Data" "Max Corner Data") (Type String)(Default "Normal Corner Data") (Description "Text string that varies by corner") ) ) | End Model_Specific ) | End test ****************************************************************************** ******************** BELOW FOR ADMINISTRATION AND TRACKING ******************* ****************************************************************************** BUG NUMBER: 109 SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] SEVERE PRIORITY: [HIGH, MEDIUM, LOW] HIGH STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] CLOSED FIXED VERSION: Version 5.0.2 FIXED DATE: January 30, 2010 NOTES ON BUG FIX: Classified at IBIS Teleconference Meeting on December 11, 2009 Noted that added that this problem also applies to Boolean types, but complete checking of the Type argument with the actual Value entry is not officially part of BIRD109 To be fixed in the next release Checked January 30, 2010 ****************************************************************************** ******************************************************************************