This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/9398] Bug in ffi.h.in header file
- From: "a dot rottmann at gmx dot at" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Oct 2003 02:02:15 -0000
- Subject: [Bug other/9398] Bug in ffi.h.in header file
- References: <20030122083600.9398.theller@python.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9398
------- Additional Comments From a dot rottmann at gmx dot at 2003-10-27 02:02 -------
The ffi.h[.in] file changed a bit since the gcc 3.3.2 release. Now it blatantly
says:
#define ffi_type_ulong ffi_type_uint64
#define ffi_type_slong ffi_type_sint64
without any condition (the other types seem OK now). I cannot image that this is
intended behavior -- there should be ffi_type_[us]long _and_
ffi_type_[us]long_long types; how would you else describe a function that takes
(or returns) a 'long' -- you cannot tell for sure that long is a specific size...