From: u-xsnf@aetey.se
To: Richard Henderson <rth@redhat.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: showstopper bug on x86 (Re: libffi does not follow proper ABI on ia32)
Date: Wed, 24 Dec 2014 21:35:00 -0000 [thread overview]
Message-ID: <20141224213437.GH14316@example.net> (raw)
In-Reply-To: <549AEA51.2000500@redhat.com>
Thanks Richard,
for the reply and the confirmation!
On Wed, Dec 24, 2014 at 08:31:13AM -0800, Richard Henderson wrote:
> On 12/24/2014 05:58 AM, u-xsnf@aetey.se wrote:
> > Nevertheless I would appreciate at least hints about the prospect to fix
> > this bug (apparently non-conformant C ABI of libffi on x86 Linux),
> > which presumably went unnoticed for a long time due to gcc not exercising
> > the full ABI.
>
> Yes, I see the problem. Fixing it may have to wait until the new year.
This is fortunately not a very long time to come :)
Looking forward to a fix - when you find time for it.
Regards,
Rune
next prev parent reply other threads:[~2014-12-24 21:35 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 [this message]
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 ` libffi vs pcc (was: showstopper bug on x86 / " u-xsnf
2015-01-06 16:20 ` showstopper bug on x86 (Re: " 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=20141224213437.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).