Would lint be able to detect 32 to 64-bit porting issues?

mshetty (mshetty@mail.com) wrote:
: Would lint be able to detect 32 to 64-bit porting issues?

There is no lint on IPF.

======================
From: mshetty@mail.com (mshetty)
>"Run the application as a 32-bit application on the 64-bit platform.
>In other words do not use creat64 instead of creat?"

If you are in 64 bit mode, you call creat(2) and not creat64(2).
You only use creat64 in 32 bit mode after you've set -D_LARGEFILE_SOURCE
and possibly -D_FILE_OFFSET_BITS=64.

>PS: To identify porting issues, is compilation a good option? I mean
>would the compiler throw warnings or errors for some/all of the issues
>encountered while porting?
M Shetty

It depends.

>From: "Magnus Bengtsson" <Magnus.Bengtsson@atosorigin.com>
>Depends on how well written your old code is... :-)

Right.

>HP's C compiler has an option +M2 that catches many of the problems with
>mixed integral types when porting to 64-bit. Don't know if it exists for
>IPF, though.

+M2 doesn't exist until A.05.55, coming out right about now.

>(According to the documentation on docs.hp.com the IPF compiler does support
>+M2, and +M1 will issue warnings about IPF migration problems.)
Magnus

(There no longer is an +M1 option on IPF.)

How did you find about +M2? I can only find A.05.55 if I search.