Shutting up the warnings would be useful (for Perl) if I was convinced they were all false alarms, but I'm semi-convinced that one or more of them is the reason behind some traps I experience when I get close to allocating 4GB of virtual memory.

For Parrot, which effectively equates sizeof( INTVAL ) == sizeof( void* ) all over the show, I'm convinced that the configuration utility (that actually warns of the problem), is doing the wrong thing with respect to how it defines the fundemental typedefs.

Personally, I think that on windows the following typedefs for STRLEN, IV and UV should be used. And most (if not all) uses of int, I32, and U32 should dropped in favour of one if the 3 above.

#include <stdio.h>
#include <stddef.h>

typedef uintptr_t UV;
typedef ptrdiff_t STRLEN;
typedef intptr_t  IV;

#ifdef _WIN64
#define IS_WIN64 ""
#else
#define IS_WIN64 "not"
#endif


void main( void ){
    printf( "_WIN64 is %s defined\n", IS_WIN64 );
    printf( "MAX: %d\n", _INTEGRAL_MAX_BITS );
    printf( "size_t    is %d bytes\n", sizeof( size_t ) );
    printf( "int       is %d bytes\n", sizeof( int ) );
    printf( "long      is %d bytes\n", sizeof( long ) );
    printf( "long long is %d bytes\n", sizeof( long long ) );
    printf( "UV        is %d bytes\n", sizeof( UV ) );
    printf( "IV        is %d bytes\n", sizeof( IV ) );
    printf( "STRLEN    is %d bytes\n", sizeof( STRLEN ) );
}
[download]

Compiled for 32 & 64-bit targets this produces:

C:\test>size_t.exe
_WIN64 is not defined
MAX: 64
size_t    is 4 bytes
int       is 4 bytes
long      is 4 bytes
long long is 8 bytes
UV        is 4 bytes
IV        is 4 bytes
STRLEN    is 4 bytes

C:\test>size_t.exe
_WIN64 is  defined
MAX: 64
size_t    is 8 bytes
int       is 4 bytes
long      is 4 bytes
long long is 8 bytes
UV        is 8 bytes
IV        is 8 bytes
STRLEN    is 8 bytes
[download]