From: Jasper Lievisse Adriaanse <jasper@humppa.nl>
To: libffi-discuss@sources.redhat.com
Subject: Re: libffi 3.0.9 release candidate 1
Date: Mon, 05 Oct 2009 18:08:00 -0000 [thread overview]
Message-ID: <20091005180808.GC29614@gurthang.humppa.nl> (raw)
In-Reply-To: <20091005180653.GB29614@gurthang.humppa.nl>
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
On Mon, Oct 05, 2009 at 08:06:53PM +0200, Jasper Lievisse Adriaanse wrote:
> On Mon, Oct 05, 2009 at 12:57:30AM -0400, Anthony Green wrote:
> > Here's 3.0.9rc1:
> > ftp://sources.redhat.com/pub/libffi/libffi-3.0.9rc1.tar.gz
> >
> > I built this out of my new git repository here:
> > http://github.com/atgreen/libffi
> >
> > I'm using stgit, which is like quilt for git. I rebased the git
> > repository to gcc HEAD, then added the "stand-alone" patches (mostly
> > configury changes), the AVR port, the Snow Leopard memory protection
> > fix, and the 64-bit AIX fix.
> >
> > I believe we're missing ChangeLog entries from Jens, Abdulaziz, and
> > Bradley. Please send them. I'll push your changes into GCC once
> > they're clean.
> >
> > Abdulaziz - please also check that I applied your patch correctly.
> > The source files had changed somewhat since you submitted it.
> >
> > I'll set up a wiki page to track platform testing soon, but initial
> > test results and pointers to missing patches would be helpful.
> >
> > Thanks,
> >
> > AG
>
> As of this RC, there's an increase of about 340 in failed tests on
> OpenBSD. I've attached the log. The unwindtest.cc failure is expected,
> ther others not. Anyone has a clue what's going on here?
>
> libffi 3.0.8:
> # of expected passes 1365
> # of unexpected failures 8
> # of unsupported tests 15
>
> libffi 3.0.9rc1
> # of expected passes 685
> # of unexpected failures 348
> # of unsupported tests 15
>
> Cheers,
> Jasper
>
> --
> "Intelligence should guide our actions, but in harmony with the
> texture of the situation at hand"
> -- Francisco Varela
this time with the log *attached*..
[-- Attachment #2: libffi.log.gz --]
[-- Type: application/x-gunzip, Size: 23443 bytes --]
next prev parent reply other threads:[~2009-10-05 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 4:57 Anthony Green
2009-10-05 18:07 ` Jasper Lievisse Adriaanse
2009-10-05 18:08 ` Jasper Lievisse Adriaanse [this message]
2009-10-05 18:21 ` Anthony Green
2009-10-05 18:23 ` Anthony Green
2009-10-05 18:29 ` Jasper Lievisse Adriaanse
2009-10-05 20:01 ` Jasper Lievisse Adriaanse
2009-10-05 18:25 ` Jasper Lievisse Adriaanse
2009-10-05 20:21 ` Andreas Tobler
2009-10-05 20:31 ` Jasper Lievisse Adriaanse
2009-10-05 20:36 ` Andreas Tobler
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=20091005180808.GC29614@gurthang.humppa.nl \
--to=jasper@humppa.nl \
--cc=libffi-discuss@sources.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).