This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: libffi fails to build on powerpc64-linux
- From: Peter Bergner <bergner at vnet dot ibm dot com>
- To: dclarke at blastwave dot org
- Cc: libffi-discuss at sourceware dot org, Anthony Green <green at moxielogic dot com>
- Date: Mon, 05 Mar 2012 17:29:16 -0600
- Subject: Re: libffi fails to build on powerpc64-linux
- References: <64185.10.0.66.17.1330988704.squirrel@interact.purplecow.org>
On Mon, 2012-03-05 at 18:05 -0500, Dennis Clarke wrote:
> > After the latest libffi merge into GCC, GCC no longer builds on
> > powerpc64-linux due to the following errors:
>
> I ran into a bucket of issues with libffi also :
>
> http://sourceware.org/ml/libffi-discuss/2012/msg00048.html
>
> May or may not be related.
Not related, since I'm not even getting past the build, let alone
firing off the testsuite. I'll let you know what happens when
I get that far. :)
That said, adding your --enable-debug configure option, I see a few
other changes that should be made to silence some warnings about
casting a pointer to an integer of a different size (ie, smaller):
@@ -155,9 +156,9 @@ ffi_prep_args_SYSV (extended_cif *ecif, unsigned
*const stack)
next_arg.u = stack + 2;
/* Check that everything starts aligned properly. */
- FFI_ASSERT (((unsigned) (char *) stack & 0xF) == 0);
- FFI_ASSERT (((unsigned) copy_space.c & 0xF) == 0);
- FFI_ASSERT (((unsigned) stacktop.c & 0xF) == 0);
+ FFI_ASSERT (((unsigned long) (char *) stack & 0xF) == 0);
+ FFI_ASSERT (((unsigned long) copy_space.c & 0xF) == 0);
+ FFI_ASSERT (((unsigned long) stacktop.c & 0xF) == 0);
FFI_ASSERT ((bytes & 0xF) == 0);
FFI_ASSERT (copy_space.c >= next_arg.c);
Peter