Hi ,
I would point you Section 1.10 of the the OpenVMS CRTL manual where there is a good discussion of mixing and 32bit and 64 bit pointers in the same application . free is a function that accepts both 32bit and 64 bit pointers . In order to allocate 32 bit memory in 64 bit application you need to call _malloc32. So if you if you do
void *(*realloc_func)(void *, size_t) = _realloc32;
it will silence the compiler when compiled with /POINTER=32. There is nothing you can do to silence free , since it is designed to accept both 32 bit and 64 bit pointers. As a good programmer, I understand that it is annoying to find warnings when it is not your fault.
One caveat you need to be careful though:
The the 32 bit and 64 bit malloc calls corresponding lib$ routines in librtl. There is no communication between these 32 bit and 64 bit librtl routines. 32 bit routines allocate memory from P0 and 64 bit from P2 space. So if you allocate memory in 32bit space and use realloc64 to copy it will fail.
But in the program given below, if you remove the first line , you will find that librtl allocates the requested size. But this is because no malloc64 is not yet called, so it thinks it is a fresh allocation.
complile with /POINTER=LONG
#include
#include
int main()
{
char *test = malloc(1); /* remove this line to see the issue */
__char_ptr32 c1 = (__char_ptr32)_malloc32(1);
*c1 = 'x';
printf("%08llx : <%c>\n", c1, *c1);
char* c2 = (char*)realloc(c1, 10000); /* force reallocation */
if( c2 == NULL)
{
printf(" Realloc fails !" );
}
return EXIT_FAILURE;
}
--Lucifer
"To Denouce the Evils of Truth and Love. To cause may hem and destruction and necromancy , Lucifer is here"
