Launchpad has imported 8 comments from the remote bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12782.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://documentation.ubuntu.com/launchpad/user/reference/bugs/multi-project-bugs/about-multi-project-bugs/#bugs-in-external-trackers.

------------------------------------------------------------------------
On 2003-10-27T00:43:16+00:00 Andreas Rottmann wrote:

The way ffi.h #defines the ffi_type_XX equivalents to the standard C
types seems bad - they are mixed along with the #defines of the
fixed-bit types (e.g. UINT32), but the two issues are orthogonal. 

This results in ffi_type_ulong, for instance, being #defined to ffi_type_uint64
on (at least) x86, as the following test program indicates:

#include <stdio.h>
#include <ffi.h>

int main ()
{
  printf ("&ffi_type_ulong: %p &ffi_type_uint64: %p\n", 
          &ffi_type_ulong, &ffi_type_uint64);
}

This results in the following output on my Athlon (no, no Athlon64 yet
;-))

&ffi_type_ulong: 0x8049738 &ffi_type_uint64: 0x8049738

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/0

------------------------------------------------------------------------
On 2003-10-27T00:47:28+00:00 Andreas Rottmann wrote:

Created attachment 5005
Fix ffi_type_X #defines

The patch should fix this bug, makes the #ifdef nesting more readable by using
#elif and adds #defines for 'long long' and 'unsigned long long'.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/1

------------------------------------------------------------------------
On 2003-10-27T00:55:12+00:00 Pinskia wrote:

*** Bug 9398 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/2

------------------------------------------------------------------------
On 2003-10-27T00:58:13+00:00 Pinskia wrote:

Could you patch the one in the sources called ffi.h.in (make sure that it is 
the mainline sources) in 
gcc/libffi/include and make a changelog and post the patch with the changelog 
to gcc-
[email protected].  Note GCC is not the official maintainers of libffi yet.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/3

------------------------------------------------------------------------
On 2003-10-27T09:48:57+00:00 Andreas Rottmann wrote:

The ffi.h[.in] file changed a bit since the gcc 3.3.2 release. Now (in CVS) 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...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/4

------------------------------------------------------------------------
On 2003-10-31T06:14:55+00:00 Green-c wrote:

Yes, this is wrong.  We should use tests to define ffi_type_[us]long like the
other types descriptors above it.
 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/5

------------------------------------------------------------------------
On 2005-11-06T18:41:35+00:00 Green-c wrote:

Created attachment 10159
A patch

I think the attached patch will fix.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/6

------------------------------------------------------------------------
On 2007-08-10T09:18:23+00:00 Green-c wrote:

I believe the patch for this was checked in a long time ago.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.1/+bug/72505/comments/11

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/72505

Title:
  python2.5 compiled with libffi does not support ctypes 64 bits integer

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/72505/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to