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

2007-03-09 Thread Kai Tietz
PROTECTED] 08.03.2007 19:08 To Kai Tietz [EMAIL PROTECTED] cc Ian Lance Taylor [EMAIL PROTECTED], gcc@gcc.gnu.org Subject Re: What does coding-style tells about integer types for pointers ? On Thu, Mar 08, 2007 at 06:06:57PM +0100, Kai Tietz wrote: In gcc the file emutls.c assumes that a long

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

2007-03-09 Thread Andrew Haley
Please stop top-posting. Kai Tietz writes: Richard Henderson [EMAIL PROTECTED] 08.03.2007 19:08 On Thu, Mar 08, 2007 at 06:06:57PM +0100, Kai Tietz wrote: In gcc the file emutls.c assumes that a long has sizeof void * in function emutls_destroy. Not really. It

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

2007-03-08 Thread Kai Tietz
Hi, 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

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

2007-03-08 Thread DJ Delorie
I found this problems until now in libc++, libiberty. Could you be more specific about the libiberty ones?

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

2007-03-08 Thread Kai Tietz
: +49-941-78004-0 FAX: +49-941-78004-489 WWW: http://www.OneVision.com DJ Delorie [EMAIL PROTECTED] 08.03.2007 17:04 To [EMAIL PROTECTED] cc gcc@gcc.gnu.org Subject Re: What does coding-style tells about integer types for pointers ? I found this problems until now in libc

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

2007-03-08 Thread DJ Delorie
In libiberty I found the following points. Do any of these cause real failures?

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

2007-03-08 Thread Kai Tietz
://www.OneVision.com DJ Delorie [EMAIL PROTECTED] 08.03.2007 17:30 To [EMAIL PROTECTED] cc gcc@gcc.gnu.org Subject Re: What does coding-style tells about integer types for pointers ? In libiberty I found the following points. Do any of these cause real failures?

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

2007-03-08 Thread Joseph S. Myers
On Thu, 8 Mar 2007, Kai Tietz wrote: 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

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

2007-03-08 Thread Kai Tietz
Phone: +49-941-78004-0 FAX: +49-941-78004-489 WWW: http://www.OneVision.com Ian Lance Taylor [EMAIL PROTECTED] 08.03.2007 18:02 To Kai Tietz [EMAIL PROTECTED] cc gcc@gcc.gnu.org Subject Re: What does coding-style tells about integer types for pointers ? Kai Tietz [EMAIL PROTECTED

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

2007-03-08 Thread Kai Tietz
: +49-941-78004-0 FAX: +49-941-78004-489 WWW: http://www.OneVision.com Joseph S. Myers [EMAIL PROTECTED] 08.03.2007 18:00 To Kai Tietz [EMAIL PROTECTED] cc gcc@gcc.gnu.org Subject Re: What does coding-style tells about integer types for pointers ? On Thu, 8 Mar 2007, Kai Tietz wrote

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

2007-03-08 Thread Joseph S. Myers
On Thu, 8 Mar 2007, Kai Tietz wrote: As I know, the types are declared in config/stdint.m4, which is part of gcc, isn't it ? There are many different things part of GCC can mean. Different parts of GCC may wish to know these types for the build system, for the host system or for the target

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

2007-03-08 Thread Richard Henderson
On Thu, Mar 08, 2007 at 06:06:57PM +0100, Kai Tietz wrote: In gcc the file emutls.c assumes that a long has sizeof void * in function emutls_destroy. Not really. It assumes you can store the size of the array in min(sizeof(long), sizeof(void*)) bytes. r~