From: "Maciej W. Rozycki" <macro@wdc.com>
To: libffi-discuss@sourceware.org
Subject: [PING][PATCH libffi 0/4] Robustify compiler and library path selection in the testsuite
Date: Tue, 14 Apr 2020 14:59:04 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2004141451570.461@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2004012222200.461@redsun52.ssa.fujisawa.hgst.com>
On Fri, 3 Apr 2020, Maciej W. Rozycki wrote:
> We are keen to keep the GCC's copy of libffi as close as possible to the
> upstream version however while usable the current solution has some issues
> which we would rather avoid. I have therefore decided to address some of
> them with the intent to have the result backported to GCC. As it stands
> I'm told the current version of libffi cannot be fully merged to GCC, as
> there have been an ABI change that will require technical evaluation. So
> the intent has been to backport the changes proposed here individually.
>
> See the individual change descriptions and any further discussion
> included for full details of each patch proposed.
Ping for:
<https://sourceware.org/pipermail/libffi-discuss/2020/002503.html>
<https://sourceware.org/pipermail/libffi-discuss/2020/002504.html>
<https://sourceware.org/pipermail/libffi-discuss/2020/002505.html>
<https://sourceware.org/pipermail/libffi-discuss/2020/002506.html>
Maciej
next prev parent reply other threads:[~2020-04-14 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 22:55 [PATCH " Maciej W. Rozycki
2020-04-03 22:55 ` [PATCH libffi 1/4] Use a template to pass $CC and $CXX to DejaGNU Maciej W. Rozycki
2020-04-06 17:58 ` Jeff Law
2020-04-03 22:55 ` [PATCH libffi 2/4] Use a documented way to pass $compiler_vendor " Maciej W. Rozycki
2020-04-06 18:00 ` Jeff Law
2020-04-03 22:56 ` [PATCH libffi 3/4] Make `libffi-init' use $CC_FOR_TARGET Maciej W. Rozycki
2020-04-06 18:03 ` Jeff Law
2020-04-03 22:56 ` [PATCH libffi 4/4] Correct indentation throughout `libffi-init' Maciej W. Rozycki
2020-04-06 18:01 ` Jeff Law
2020-04-14 13:59 ` Maciej W. Rozycki [this message]
2020-04-20 12:50 ` [PING^2][PATCH libffi 0/4] Robustify compiler and library path selection in the testsuite Maciej W. Rozycki
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=alpine.LFD.2.21.2004141451570.461@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=libffi-discuss@sourceware.org \
/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).