What does coding-style tells about integer types for pointers ?

[Kai Tietz]

In gcc the file emutls.c assumes that a long has sizeof void * in function 
emutls_destroy.

Regards,
 i.A. Kai Tietz

----------------------------------------
  Kai Tietz - Software engineering
  OneVision Software Entwicklungs GmbH & Co KG
  Dr.-Leo-Ritter-Str. 9, 93049 Regensburg, Germany
  Phone: +49-941-78004-0
  FAX:   +49-941-78004-489
  WWW:   http://www.OneVision.com



Ian Lance Taylor <iant@google.com> 
08.03.2007 18:02

To
Kai Tietz <Kai.Tietz@onevision.com>
cc
gcc@gcc.gnu.org
Subject
Re: What does coding-style tells about integer types for pointers ?






Kai Tietz <Kai.Tietz@onevision.com> writes:

> while porting gcc to the new target x86_64-pc-mingw32 I noticed, that on 

> many places the long type is wrongly used as equivalent for pointers. 
This 
> leads for this MS compatible target to some problems, because the long 
is 
> just 4 bytes long and the pointer 8 bytes. I found this problems until 
now 
> in libc++, libiberty. There are ISO types defined for this case, as 
> intptr_t  and uintptr_t. Is there something defined in the coding style 
?

Code in gcc which assumes that sizeof (long) == sizeof (void *) is
broken.  Tell us where that code is, and we will try to fix it.

Ian