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: Tue, 06 Jan 2015 16:52:00 -0000 [thread overview]
Message-ID: <20150106165212.GL14316@example.net> (raw)
In-Reply-To: <54AC0B5B.9010206@redhat.com>
On Tue, Jan 06, 2015 at 08:20:43AM -0800, Richard Henderson wrote:
> On 01/06/2015 02:21 AM, u-xsnf@aetey.se wrote:
> > I wonder which version of pcc you were testing with, the comments
> > about the pcc behaviour indicate that the version used was either
> > too old or its install was broken (pcc used to ship redundant and
> > in practice harmful startup files, not actually being a part of the compiler).
>
> I was using
>
> pcc 1.1.0.DEVEL 20140817 for i686-pc-linux-gnu
>
> as shipped with fedora 21.
The version does not look utterly old (even though much has happened
since then) but the Fedora packaging people were apparently misled by
the then badly documented data, which results in a quite broken package.
Now this is cleaned up and somewhat documented upstream, so future pcc
packages, for Fedora or otherwise, will be hopefully better.
Rune
prev parent reply other threads:[~2015-01-06 16:52 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 ` 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 [this message]
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=20150106165212.GL14316@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).