From: u-xsnf@aetey.se
To: Richard Henderson <rth@redhat.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi vs pcc (was: showstopper bug on x86 / libffi does not follow proper ABI on ia32)
Date: Tue, 06 Jan 2015 12:46:00 -0000 [thread overview]
Message-ID: <20150106124609.GH14316@example.net> (raw)
In-Reply-To: <20150106102102.GF14316@example.net>
On Tue, Jan 06, 2015 at 11:21:02AM +0100, u-xsnf@aetey.se wrote:
> 306 of the still failing tests try to test FASTCALL and THISCALL which
> is not expected to pass. At least some of the remaining 210 ones quite
> probably depend on a bug in pcc which was independently discovered this
> week and fixed
> Moreover, at about the same time pcc seems to have got support for fastcall (!)
> I am going to make the next round with the newest pcc and see how many
> test failures remain.
The fastcall support in pcc is not yet complete.
I was able to compile libffi both with HAVE_FASTCALL=0 and HAVE_FASTCALL=1
and it looks mostly working in both cases (nice!).
Yet many tests are still failing, both related and unrelated to fastcall -
I'll take this up on the pcc list.
Rune
next prev parent reply other threads:[~2015-01-06 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 19:36 libffi does not follow proper ABI on ia32 (?) u-xsnf
2014-12-24 13:58 ` showstopper bug on x86 (Re: libffi does not follow proper ABI on ia32) u-xsnf
2014-12-24 16:31 ` Richard Henderson
2014-12-24 21:35 ` u-xsnf
2014-12-31 16:12 ` Richard Henderson
2015-01-02 18:57 ` u-xsnf
2015-01-02 22:20 ` Richard Henderson
2015-01-03 10:15 ` u-xsnf
2015-01-03 10:36 ` u-xsnf
2015-01-05 21:34 ` Richard Henderson
2015-01-06 10:21 ` u-xsnf
2015-01-06 12:46 ` u-xsnf [this message]
2015-01-06 16:20 ` Richard Henderson
2015-01-06 16:52 ` u-xsnf
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=20150106124609.GH14316@example.net \
--to=u-xsnf@aetey.se \
--cc=libffi-discuss@sourceware.org \
--cc=rth@redhat.com \
/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).