public inbox for
 help / color / mirror / Atom feed
From: Anthony Green <>
To: libffi-discuss <>
Subject: Please help prep for a new libffi release
Date: Wed, 7 Sep 2022 09:44:57 -0400	[thread overview]
Message-ID: <> (raw)

I'd like to start prepping for a new release.

Over the past couple of weeks I've made some improvements to the
Github Actions CI infrastructure, notably taking advantage of the GCC
Compile Farm to test a number of previously untested platforms,
including the new loongarch64 port, Solaris, AIX, Aarch64, including
an M1 Linux host, and several combinations of macos & compiler -- 21
platforms in all.

The CI tests all come up green today, so it should be easy to track
regressions as we go through any patch backlog.

The test results, however, are not all perfect.  Some ports are still
not passing struct args by value, the Cygwin results are a mess
(uninvestigated), and some of the qemu-based testing is broken (eg.
m68k, s390).  The complete list of problems is available here:

If you aren't familiar with "red light green light", this file
contains pattern matching expressions we use to filter the dejagnu
results in order to decide whether or not a test run is "good enough".
It doesn't make sense to xfail tests in the dejagnu test source when
the problem is in the simulator we're testing with, so we use rlgl as
a higher-level tool to evaluate the test results with an extra layer
of "expected fail" policy.

Any additional eyes-on or help with known problems would be
appreciated.  Also, if you are sitting on any patches, please let me



             reply	other threads:[~2022-09-07 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:44 Anthony Green [this message]
2022-09-12 14:19 ` Anthony Green
2022-09-18 22:25   ` 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:

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

  git send-email \ \ \ \

* 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).