From: Matthias Klose <doko@ubuntu.com>
To: Tom Tromey <tom@tromey.com>, Anthony Green <green@moxielogic.com>
Cc: libffi-discuss <libffi-discuss@sourceware.org>,
s.mesoraca16@gmail.com, "H.J. Lu" <hjl.tools@gmail.com>,
arigo@tunes.org, landonf@freebsd.org
Subject: Re: Another libffi ABI change and another release
Date: Mon, 13 Jul 2020 11:58:23 +0200 [thread overview]
Message-ID: <d24fe445-4ef4-8728-a530-ab466faa4f0f@ubuntu.com> (raw)
In-Reply-To: <8736ayha1j.fsf@tromey.com>
On 2/25/20 6:05 PM, Tom Tromey wrote:
> Anthony> Yes, some of them were related to trampoline layouts, which aren't relevant
> Anthony> if we go this route...
> Anthony> http://sourceware-org.1504.n7.nabble.com/Crashes-of-libffi-when-using-W-X-memory-and-forks-td412729.html
> Anthony> ...which is what I'd like to do.
>
> The ones I was thinking of were in this thread
>
> https://sourceware.org/ml/libffi-discuss/2015/msg00090.html
>
> But AFAIK there aren't patches for any of these ideas.
I have now the request to enable CET in a distro, and before bumping the soname
myself, or invent an arbitrary soname which won't be used by upstream, I'd like
to ask if an upstream release could be cut now, without repeating the multi-year
release process we had with libffi 3.3.
Thanks, Matthias
next prev parent reply other threads:[~2020-07-13 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 1:07 Anthony Green
2020-02-24 23:21 ` Tom Tromey
2020-02-24 23:31 ` Anthony Green
2020-02-25 17:05 ` Tom Tromey
2020-07-13 9:58 ` Matthias Klose [this message]
2020-07-13 10:47 ` Florian Weimer
2020-07-13 11:03 ` Matthias Klose
2020-07-13 11:10 ` Florian Weimer
2020-11-11 14:40 ` Matthias Klose
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=d24fe445-4ef4-8728-a530-ab466faa4f0f@ubuntu.com \
--to=doko@ubuntu.com \
--cc=arigo@tunes.org \
--cc=green@moxielogic.com \
--cc=hjl.tools@gmail.com \
--cc=landonf@freebsd.org \
--cc=libffi-discuss@sourceware.org \
--cc=s.mesoraca16@gmail.com \
--cc=tom@tromey.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).