public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: Tom Tromey <tom@tromey.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, 24 Feb 2020 23:31:00 -0000	[thread overview]
Message-ID: <CACxje58CD_8Db7nL=zMKaurLA+h4MXtxxOtSQ2nO-CGEo+5VTA@mail.gmail.com> (raw)
In-Reply-To: <871rqjmv05.fsf@tromey.com>

On Mon, Feb 24, 2020 at 6:21 PM Tom Tromey <tom@tromey.com> wrote:

> I don't know if there are urgent ones (certainly I don't have anything
> written) but I think a while back there was a thread about a wish-list
> for ABI breaks.  But perhaps if we're breaking ABI now, it could be done
> again in the future.
>

Yes, some of them were related to trampoline layouts, which aren't relevant
if we go this route...
http://sourceware-org.1504.n7.nabble.com/Crashes-of-libffi-when-using-W-X-memory-and-forks-td412729.html
...which is what I'd like to do.

Landon Fuller came up with this hack for the iOS port, but it seems that it
is generally useful, and would solve a number of issues.

AG

  reply	other threads:[~2020-02-24 23:31 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 [this message]
2020-02-25 17:05     ` Tom Tromey
2020-07-13  9:58       ` Matthias Klose
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='CACxje58CD_8Db7nL=zMKaurLA+h4MXtxxOtSQ2nO-CGEo+5VTA@mail.gmail.com' \
    --to=green@moxielogic.com \
    --cc=arigo@tunes.org \
    --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).