Conference hydra::axp-developer

3361.0. "Greystone" by HYDRA::BRYANT () Wed Mar 19 1997 16:26

    Company Name :  Greystone
    Contact Name :  Bob Lidral
    Phone        :  
    Fax          :  
    Email        :  [email protected]
    Date/Time in :  19-MAR-1997 16:25:34
    Entered by   :  Pat Bryant
    SPE center   :  MRO

    Category     :  UNIX
    OS Version   :  
    System H/W   :  


    Brief Description of Problem:
    -----------------------------
To: [email protected]
Subject: 32-bit pointer support
Cc: [email protected]

Hi,

We have a product running on Digital Unix that requires 32-bit pointer support.
It already works on V3.2, but we are upgrading to a new Digital Unix release.
In doing so, it is necessary for us to run our own (slightly modified) version
of xtaso_header_edit as described in the Programmer's Guide, Appendix A.

When I attempted to run this, it worked OK, but didn't modify all of the
requisit header files.  If you examine the script closely, you'll note it
processes the directory trees /usr/include and /sys/include, but doesn't
follow symbolic links.  Unfortunately, in going from V3.2 to V4.0 of Digital
Unix, /sys/include has become a symbolic link to /usr/sys/include, so the header
files in that directory don't get modified by xtaso_header_edit.

My questions:

	1.  Am I reading the manual incorrectly?

	2.  I can modify our version of xtaso_header_edit to handle both
	    versions of Digital Unix, but need to know whether /usr/include
	    and /usr/sys/include are sufficient on V4.0 or whether I should
	    also point it at some other directory?


Related question:

	1.  We are (slowly) moving from a 32-bit pointer environment through
	    a mixed 32-bit/64-bit pointer environment with some possibility
	    of ending up in a unified 64-bit pointer environment (though not
	    any time soon).  It would help us if lint could detect assignments
	    from 64-bit to 32-bit pointers in the same manner as it detects
	    assignments from long to {int,short} and from int to short.  Is
	    that feature available with lint on Digital Unix V4.0 (it did not
	    appear to be on V3.2)?



Thanks.



Bob Lidral
[email protected]

Bob,

I apologize for the delay with your questions.  I have posted the one about the 
xtaso_header_edit script to Digital UNIX Engineering.  I will relay any 
information I have for you.  I expect to hear something this afternoon or 
tomorrow.

Also, I am currently researching for a tool that will help detect 64-bit to 
32-bit pointer assignments.

Thanks for your patience,
Pat Bryant
Alpha Developer Support

Bob,

Engineering reported back that you can modify your xtaso_header_edit script to 
get it working.  Protecting everything under the /usr/include directory tree 
should be sufficient.   If there are special project header files where a 64-bit 
interface needs to be maintained, then the script will need to be run against 
those directories as well.

Also, they will be providing a much cleaner solution for protecting 64-bit sytem 
header files when xtaso is used in a version of DECC that is due out later this 
year.  It enables a new protect_header feature.  Look for this in a planned 
release of Digital UNIX 4.0d.

If you have any further questions related to either of these issues, feel free 
to reply back.

Thank you.
Pat Bryant
Alpha Developer Support