public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: "Dr. David Alan Gilbert" <david.gilbert@linaro.org>
Cc: libffi-discuss@sourceware.org, Marcus.Shawcroft@arm.com,
	cltang@linaro.org
Subject: PowerPC failures (Was: [PATCH] Add variadic support)
Date: Wed, 23 Feb 2011 21:16:00 -0000	[thread overview]
Message-ID: <m3sjvelabx.fsf@redhat.com> (raw)
In-Reply-To: <20110222154022.GA29862@davesworkthinkpad> (David Alan Gilbert's	message of "Tue, 22 Feb 2011 15:40:30 +0000")

"Dr. David Alan Gilbert" <david.gilbert@linaro.org> writes:

>    2) I've tested it on i386 (1659 expected passes, 15 unsupported),
>                         armel (1654 expected passes, 5 unexpecteed passes (cls_longdouble.c), 15 unsupported)
>                         armhf (1654 expected passes, 5 unexpecteed passes (cls_longdouble.c), 15 unsupported)
>                         s390x (1639 expected passes, 5 unexpected failures - err_bad_abi.c)
> 		Those cls_longdouble unexpected passes and err_bad_abi.c
> 		failure are there in the current head.
> 	powerpc64 seems to be broken on current head, but I tested this patch
> 	on powerpc64 on the .0.9 release and it was OK.

I just tested the head on powerpc64-unknown-linux-gnu and had no
problems.  You appear to be testing powerpc64-unknown-linux-gnu like me,
but with a different gcc and binutils version.

You wrote on the wiki...
> Failure is src/powerpc/ffi.c:961 where cif->abi is expected to be
> FFI_GCC_SYSV or FFI_SYSV but is getting FFI_LINUX

Line 961 is only run when POWERPC64 isn't defined.

POWERPC64 is defined in src/powerpc/ffitarget.h.   Could you please see
why it's not being defined in your build environment?

Thanks!

AG

  parent reply	other threads:[~2011-02-23 21:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 15:41 [PATCH] Add variadic support Dr. David Alan Gilbert
2011-02-23 12:39 ` Anthony Green
2011-02-23 13:12   ` David Gilbert
2011-02-23 13:26     ` Chung-Lin Tang
2011-02-23 16:20       ` David Gilbert
2011-02-23 16:56         ` Chung-Lin Tang
2011-02-23 17:21           ` David Gilbert
2011-02-23 17:39             ` Chung-Lin Tang
2011-02-24  6:37               ` Chung-Lin Tang
2011-02-25 12:56               ` David Gilbert
2011-02-25 13:23                 ` Chung-Lin Tang
2011-02-25 19:02                   ` Anthony Green
2011-02-28  9:08                     ` David Gilbert
2011-03-07 18:19                   ` David Gilbert
2011-03-16  9:52                     ` Chung-Lin Tang
2011-03-16 14:12                       ` Anthony Green
2011-03-16 14:25                         ` David Gilbert
2011-02-23 21:16 ` Anthony Green [this message]
2011-02-24 10:43   ` PowerPC failures (Was: [PATCH] Add variadic support) David Gilbert
2011-02-24 22:37     ` PowerPC failures Anthony Green
2011-02-24 22:41       ` Matthias Klose
2011-02-25 19:18         ` Anthony Green

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3sjvelabx.fsf@redhat.com \
    --to=green@redhat.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=cltang@linaro.org \
    --cc=david.gilbert@linaro.org \
    --cc=libffi-discuss@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).