****************************************************************************** ********************* 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-info@freelists.org. A list of reported bugs will be maintained on ibis.org. ****************************************************************************** PARSER VERSION NUMBER: 7.0.2 PLATFORM (SPARC, HP700, PC, etc.): PC OS AND VERSION: Microsoft Windows 10 REPORTED BY: Curtis Clark, Ansys; Bob Ross, Teraspeed Labs DATE: July 15, 2021 DESCRIPTION OF BUG: BIRD186 introduced the ability to provide subdirectory path information for files referenced by an IBIS file. In the attached example, the [Algorithmic Model] keyword's Executable Sub-Param entries provide a relative path to the .dll, .so, and .ami files. Because the [IBIS Ver] of the .ibs file is 7.0, this relative path information should be legal. However, the ibischk7.0.2 parser issues errors for this path information if AMI_Version is set to 6.1 or lower: ------- IBISCHK7 V7.0.2 Checking bug217.ibs for IBIS 7.0 Compatibility... ... Reading bug217_path\bug217.ami ... Checking bug217_path/bug217.ami for AMI Version 6.1 Compatibility... ... Done Checking bug217_path/bug217.ami ... Done Reading bug217_path/bug217.ami ERROR (line 36) - bug217_path/icg_64.dll: Path cannot be specified in file name ERROR (line 36) - Code file icg_64.dll not found. ERROR (line 36) - bug217_path/bug217.ami: Path cannot be specified in file name ERROR (line 36) - Parameter file bug217.ami not found. ERROR (line 38) - bug217_path/icg_32.so: Path cannot be specified in file name ERROR (line 38) - Code file icg_32.so not found. ERROR (line 38) - bug217_path/bug217.ami: Path cannot be specified in file name ERROR (line 39) - bug217_path/icg_64.so: Path cannot be specified in file name ERROR (line 39) - Code file icg_64.so not found. ERROR (line 39) - bug217_path/bug217.ami: Path cannot be specified in file name ... Status of [Algorithmic Model] Executables for Windows 64: icg_64.so: Linux 64: Not Checked icg_32.so: Linux 32: Not Checked icg_64.dll: Win 64: Not Checked bug217_path/icg_32.dll: Win 32: Not Checked ... This IBISCHK7 executable supports Windows 64 bit only Errors : 10 File Failed ---- With AMI_Version set to 7.0, 0 Errors are reported, but the executable associated with the platform (icg_64.dll is marked as "Not Checked" below ... ... Status of [Algorithmic Model] Executables for Windows 64: bug217_path/icg_64.so: Linux 64: Not Checked bug217_path/icg_32.so: Linux 32: Not Checked bug217_path/icg_64.dll: Win 64: Not Checked bug217_path/icg_32.dll: Win 32: Not Checked ... This IBISCHK7 executable supports Windows 64 bit only Errors : 0 File Passed -------- The ibischk parser is mistakenly checking the version of the .ami file instead of the version of the .ibs file. If the AMI_Version in bug217.ami is changed from 6.0 to 7.0, then the parser issues no errors. The [IBIS_Ver] in the .ibs file should determine whether this Executable Sub-Param path information is allowed. Additional Issue: In addition, if three of the four rows in the [Algorithmic Model] are commented out, leaving only one row, then the parser issues no errors about the path information. This is true even if both the [IBIS_Ver] and AMI_Version are changed to 6.0. This path information should not be allowed if the IBIS_Ver is less than 7.0 (see BUG182). The parser should issue an error in this case. Further Issue: It is strange that 10 Error messages are issued (instead of 12). However, for a valid executable and platform combination, no messages should be issued and three executables should report as "Not Checked". ------------- INSERT IBIS FILE DEMONSTRATING THE BUG: ---------- bug217.ibs ---------- [IBIS Ver] 7.0 [File Name] bug217.ibs | [Date] July 18, 2021 [File Rev] 0.1 | [Notes] Executable models and .ami files are in the | relative subdirectory bug217_path | [Component] BUG217 | [Manufacturer] Test File, Inc. | [Package] R_pkg 0.01m NA NA L_pkg 0.001nH NA NA C_pkg 0.001pF NA NA | [Pin] signal_name model_name R_pin L_pin C_pin 1 tx_P Tx NA NA NA 2 tx_N Tx NA NA NA [Diff Pin] inv_pin vdiff tdelay_typ tdelay_min tdelay_max| 1 2 0.2 NA NA NA | [Model] Tx Model_type Output C_comp 64f 64f 64f [Model Spec] Vmeas 0.0882 0.0882 0.0882 Vref 0.0882 0.0882 0.0882 | [Algorithmic Model] Executable Win_A_32 bug217_path/icg_32.dll bug217_path/bug217.ami Executable Win_B_64 bug217_path/icg_64.dll bug217_path/bug217.ami Executable Linux_C_32 bug217_path/icg_32.so bug217_path/bug217.ami Executable Linux_D_64 bug217_path/icg_64.so bug217_path/bug217.ami | Comment three of four lines above to get false 0 Errors [End Algorithmic Model] | [Voltage Range] 0.1694 0.1694 0.1694 [Pulldown] -2.5 -0.05 -0.05 -0.05 0.0 0.0 0.0 0.0 2.5 0.05 0.05 0.05 [Pullup] -2.5 0.05 0.05 0.05 0.0 0.0 0.0 0.0 2.5 -0.05 -0.05 -0.05 [Ramp] dV/dt_r 0.052/16p 0.052/16p 0.052/16p dV/dt_f 0.052/17p 0.052/17p 0.052/17p [End] ---------- bug217.ami (put in subdirectory bug217_path) ---------- (BUG217_TEST (Reserved_Parameters (AMI_Version (Usage Info) (Type String)(Value "7.0")) (Init_Returns_Impulse (Usage Info) (Type Boolean)(Value True)) (GetWave_Exists (Usage Info)(Type Boolean)(Value True)) ) ) ----------------------------------------------------------------------- Put V6.1.4 qa executable models under relative subdirectory bug217_path ----------------------------------------------------------------------- bug217_path/icg_32.dll bug217_path/icg_64.dll bug217_path/icg_32.so bug217_path/icg_64.so ****************************************************************************** ******************** BELOW FOR ADMINISTRATION AND TRACKING ******************* ****************************************************************************** BUG NUMBER: 217 SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] SEVERE PRIORITY: [HIGH, MEDIUM, LOW] HIGH STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] CLOSED FIXED VERSION: 7.1.0 FIXED DATE: December 18, 2021 NOTES ON BUG FIX: Classified at the August 6, 2021 IBIS Open Forum meeting. To be fixed in the next release. ****************************************************************************** ******************************************************************************