public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org
Cc: libffi-discuss@sourceware.org, gofrontend-dev@googlegroups.com
Subject: Re: [PATCH 00/13] Go closures, libffi, and the static chain
Date: Wed, 05 Nov 2014 21:34:00 -0000	[thread overview]
Message-ID: <545A97BA.3030507@linux.vnet.ibm.com> (raw)
In-Reply-To: <1412973773-3942-1-git-send-email-rth@redhat.com>

What about the libffi changes that are needed to make this work on other 
platforms, like PowerPC?

On 10/10/2014 03:42 PM, Richard Henderson wrote:
> Pardon the wide distribution, the obvious hacks, and the failure
> to properly split up the largest of the libffi patches.
>
> The background here is my thread from last week[1], and Ian's reply[2],
> wherein he rightly points out that not needing to play games with
> mmap in order to implement closures for Go is a strong reason to
> continue using custom code within libgo.
>
> While that thread did have a go at implementing that custom code for
> aarch64, I still think that replicating libffi's calling convention
> knowledge for every interesting target is a mistake.
>
> So instead I thought about how I'd add some support for Go directly
> into libffi.  After all, we've got some custom code in libffi for
> Java, why couldn't Go have the same treatment?
>
> The stickler, as far as I could see, is __go_set_context.  I didn't
> like the idea of libffi needing a callback into libgo in order to
> accomplish the goal.
>
> But the comment immediately before __go_set_closure itself says
> that it would be better to use the static chain register.  So I set
> about to see how easy that would be to accomplish.  (And not for
> nothing such a change would make gccgo compiled programs faster
> by avoiding the library calls.)
>
> The following patch set enables this for x86_64, i386, and aarch64[3].
>
> The first two patches enable a static chain to be set by the front end
> on CALL_EXPRs, and to be used with indirect function calls.  The third
> patch is a horrible hack to expose this feature to the C front end.
>
> The 4th patch changes gccgo to use the static chain.  I don't bother
> with checking to see that the target has one.  All targets currently
> supported by libgo have one, so I don't really see this as a stumbling
> block.
>
> The 5th patch changes libgo to use the static chain.  I admit that I
> haven't tested this patch solo; I simply split it out of a larger patch
> for clarity.
>
> The 6th patch adds interfaces to libffi for Go; these interfaces are
> used within libgo in the 8th patch.
>
> Patches 7, 10, 11, 12, 13 are all enabling the new libffi interface on
> the aforementioned targets.  There's lots of cleanup in here, and I
> owe the libffi list smaller reviewable changes.  I ask that libffi
> ignore patches 10 and 12 for now and comment on the meat instead.
>
> Before I go too much farther down this road, I wanted to get some
> feedback.  FWIW, a complete tree can be found at [4].
>
> Thanks,
>
>
> r~
>
>
> [1] https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00098.html
> [2] https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00102.html
> [3] Except that after rebasing the tree on yesterday's trunk,
>      I discovered that i386 and aarch64 both have bootstrap
>      problems on trunk.  Ouch.
> [4] git://github.com/rth7680/gcc.git rth/go-closure
>
>
> Richard Henderson (13):
>    Make TARGET_STATIC_CHAIN allow a function type
>    Allow the front-end to create calls with a static chain
>    HACK!  Allow the static chain to be set from C
>    Use the static chain as the closure parameter from Go
>    libgo: Use the static chain for the closure
>    libffi: Add entry points for interacting with Go
>    libffi: Support go closures on x86_64
>    libgo: Use the new libffi interfaces for Go
>    libgo: Remove __go_get/set_closure
>    libffi: Rewrite aarch64
>    libffi: Support go closures on aarch64
>    libffi: Rewrite i386 sysv
>    libffi: Support go closures on i386
>
>   gcc/c-family/c-common.c             |    1 +
>   gcc/c-family/c-common.h             |    2 +-
>   gcc/c/c-parser.c                    |   29 +
>   gcc/calls.c                         |   14 +-
>   gcc/config/i386/i386.c              |   19 +-
>   gcc/config/moxie/moxie.c            |    5 +-
>   gcc/config/xtensa/xtensa.c          |    2 +-
>   gcc/doc/tm.texi                     |    2 +-
>   gcc/gimple-fold.c                   |   21 +
>   gcc/gimplify.c                      |   17 +-
>   gcc/go/go-gcc.cc                    |   44 +-
>   gcc/go/gofrontend/backend.h         |    7 +-
>   gcc/go/gofrontend/expressions.cc    |   21 +-
>   gcc/go/gofrontend/gogo.cc           |   29 +-
>   gcc/go/gofrontend/gogo.h            |   14 +
>   gcc/go/gofrontend/runtime.def       |    6 -
>   gcc/target.def                      |    6 +-
>   gcc/targhooks.c                     |    5 +-
>   gcc/testsuite/gcc.dg/static-chain.c |   31 +
>   gcc/tree-cfg.c                      |   22 +-
>   libffi/include/ffi.h.in             |   16 +
>   libffi/src/aarch64/ffi.c            | 1380 ++++++++++++++---------------------
>   libffi/src/aarch64/ffitarget.h      |   18 +-
>   libffi/src/aarch64/internal.h       |   43 ++
>   libffi/src/aarch64/sysv.S           |  557 +++++++-------
>   libffi/src/x86/ffi.c                | 1161 ++++++++++++-----------------
>   libffi/src/x86/ffi64.c              |  103 ++-
>   libffi/src/x86/ffitarget.h          |  112 ++-
>   libffi/src/x86/internal.h           |   48 ++
>   libffi/src/x86/sysv.S               | 1003 +++++++++++++++----------
>   libffi/src/x86/unix64.S             |  319 ++++----
>   libgo/go/reflect/makefunc.go        |   49 +-
>   libgo/go/reflect/makefunc_386.S     |   22 +-
>   libgo/go/reflect/makefunc_amd64.S   |   13 +-
>   libgo/go/reflect/makefunc_ffi.go    |   67 +-
>   libgo/go/reflect/makefunc_ffi_c.c   |   68 +-
>   libgo/go/reflect/value.go           |    3 +
>   libgo/runtime/go-reflect-call.c     |   10 +-
>   libgo/runtime/malloc.goc            |    8 -
>   libgo/runtime/mgc0.c                |    3 +-
>   libgo/runtime/proc.c                |   20 -
>   libgo/runtime/runtime.h             |    4 -
>   libgo/runtime/time.goc              |    3 +-
>   43 files changed, 2624 insertions(+), 2703 deletions(-)
>   create mode 100644 gcc/testsuite/gcc.dg/static-chain.c
>   create mode 100644 libffi/src/aarch64/internal.h
>   create mode 100644 libffi/src/x86/internal.h
>

  parent reply	other threads:[~2014-11-05 21:34 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 20:43 Richard Henderson
2014-10-10 20:43 ` [PATCH 04/13] Use the static chain as the closure parameter from Go Richard Henderson
2014-10-10 20:43 ` [PATCH 11/13] libffi: Support go closures on aarch64 Richard Henderson
2014-10-10 20:43 ` [PATCH 12/13] libffi: Rewrite i386 sysv Richard Henderson
2014-10-10 20:43 ` [PATCH 10/13] libffi: Rewrite aarch64 Richard Henderson
2014-10-10 20:43 ` [PATCH 05/13] libgo: Use the static chain for the closure Richard Henderson
2014-10-10 20:43 ` [PATCH 03/13] HACK! Allow the static chain to be set from C Richard Henderson
2014-10-11  0:33   ` Ian Lance Taylor
     [not found]     ` <CAMn1gO7vJOcNi218p9m32de_rrnKBrUcGF-EKP3dJwaL+8BtUw@mail.gmail.com>
2014-10-11  1:42       ` [gofrontend-dev] " Peter Collingbourne
2014-10-11  4:24         ` Richard Henderson
2014-10-13  8:10           ` Richard Biener
2014-10-13 18:46             ` Peter Collingbourne
2014-10-14 18:44   ` [PATCH v2 03/13] " Richard Henderson
2014-10-10 20:43 ` [PATCH 13/13] libffi: Support go closures on i386 Richard Henderson
2014-10-10 20:43 ` [PATCH 06/13] libffi: Add entry points for interacting with Go Richard Henderson
2014-10-10 20:43 ` [PATCH 01/13] Make TARGET_STATIC_CHAIN allow a function type Richard Henderson
2014-10-10 20:43 ` [PATCH 09/13] libgo: Remove __go_get/set_closure Richard Henderson
2014-10-10 20:43 ` [PATCH 02/13] Allow the front-end to create calls with a static chain Richard Henderson
2014-10-10 20:43 ` [PATCH 08/13] libgo: Use the new libffi interfaces for Go Richard Henderson
2014-10-10 20:43 ` [PATCH 07/13] libffi: Support go closures on x86_64 Richard Henderson
2014-10-11  0:23 ` [PATCH 00/13] Go closures, libffi, and the static chain Ian Lance Taylor
2014-11-05 21:34 ` Lynn A. Boger [this message]
2014-11-06  6:59   ` Richard Henderson
2014-11-06 12:48     ` Alan Modra
2014-11-06 13:04       ` Richard Henderson
2014-11-06 17:45         ` [gofrontend-dev] " Ian Taylor
2014-11-07  7:39           ` Richard Henderson
2014-11-07  8:50             ` Jay
2014-11-07 16:06             ` Ian Taylor
2014-11-07 23:55               ` Alan Modra
2014-11-06 13:10       ` Lynn A. Boger
2014-11-06 13:17         ` Richard Henderson
2014-12-11  9:06 ` Dominik Vogt
2014-12-11  9:21   ` Alan Modra
2014-12-11 10:31     ` [gofrontend-dev] " Dominik Vogt
2014-12-11 12:25       ` Dominik Vogt
2014-12-11 19:56         ` Richard Henderson
2014-12-12 12:06           ` Dominik Vogt
2014-12-12 18:14             ` Richard Henderson
2014-12-15  9:42               ` Dominik Vogt
2014-12-15 20:11                 ` Richard Henderson
2014-12-12 13:57     ` Dominik Vogt
2014-12-11 19:38   ` Richard Henderson

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=545A97BA.3030507@linux.vnet.ibm.com \
    --to=laboger@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=rth@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).