*****************************************************************************
******************** 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.2.1

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

OS AND VERSION: Microsoft Windows Enterprise 11

REPORTED BY: Michael Mirmak, Intel Corporation

DATE: December 22, 2023

DESCRIPTION OF BUG:

Clarification on Slash Characters and Parser Usage

INSERT IBIS FILE DEMONSTRATING THE BUG:

Executing the file below as follows shows no issues under ibischk7 7.2.1
for Microsoft Windows, when the ibischk7_64 executable is placed in a
subdirectory called “upper” *under* the directory where the test file
“bug246.ibs” is located:

.\upper\ibischk7_64.exe .\bug246.ibs
IBISCHK7 V7.2.1

Checking .\bug246.ibs for IBIS 4.2 Compatibility...

Errors  : 0

File Passed

Similar results are generated when the following command is executed from 
*within the “upper” directory*:

ibischk7_64.exe ..\bug246.ibs

However, using forward slashes in any of the commands above will generate an 
error similar to the following:

        ibischk7_64.exe ../bug246.ibs

IBISCHK7 V7.2.1

Checking ../bug246.ibs for IBIS 4.2 Compatibility...

ERROR (line    3) -
    File name opened '../bug246.ibs' not the same as File_name 'bug246.ibs'.

Errors  : 1

File Failed

From the error result, the parser is clearly able to open the file (a more 
complex IBIS file containing incorrect syntax will be correctly parsed even
with the forward slashes).  The operating system and the parser work together
to pass the correct file information to the parser, which the parser then
opens and checks.

The issue instead is that, as confirmed by the parser developer, the parser 
is explicitly rejecting the use of forward slashes in an operating system
(Microsoft Windows) that prefers backslash.  However, Windows supports and
automatically converts forward slashes to backward slashes.  Further, there
is no specific guidance in the IBIS document regarding how IBIS files are to
be accessed; any guidance about slash characters refers to file names 
*inside* the IBIS file and referenced files.

IBISCHK7 should support command line arguments with directories deliminated
by "/" and "\" in Windows.

|****************************************************************************
|
[IBIS Ver]     4.0
[File Name]    bug246.ibs
[File Rev]     1.0
[Date]         December 23, 2023
[Source]       Modified from fulltest.ibs, supplied with the IBISCHK
               test suite
|
[Notes]        This is to test slashes in IBISCHK usage under Microsoft 
               Windows
|****************************************************************************
|
[Component]       BUG246
[Manufacturer]    NoName
|
[Package]
|Variable     Typ               Min             Max
R_pkg         0                 0               0
L_pkg         0                 0               0
C_pkg         0                 0               0
|
|
[Pin] signal_name       model_name             R_pin    L_pin       C_pin
10    Vcc               POWER
1     Bug246            Bug246
11    Gnd               GND
|
[Model]         Bug246
Model_type      Input
|
Vinl = 0.25
Vinh = 0.75
|                             typ        min        max
C_comp                      0.525p     0.4p       0.65p
[Voltage Range]             0.850      0.750      1.125
|
[End]


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

BUG NUMBER:  246

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

PRIORITY: [HIGH, MEDIUM, LOW]                               MEDIUM

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

FIXED VERSION:

FIXED DATE:

NOTES ON BUG FIX:
Introduced to the IBIS Open Forum on January 26, 2024.

***

According to the parser developer:

"I see in the original posting by Mike that he is using ‘/’ forward slash
as the path delimiter on windows. That could be the reason that he is seeing
the error.

Running a test using ibischk7_64 under Microsoft* Windows shows the same
error when the tested file and the parser are in separate directories, even
when correct relative directory locations are used.  

For example, using an IBISCHK7 test file which is one directory *below*
the location of the ibischk7_64.exe executable:

ibischk7_64 ./upper/fulltest.ibs 

I don’t believe the spec specifies anything about the path delimiter to
be used in the command line arguments."

****


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