This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: [PATCH 00/13] Go closures, libffi, and the static chain
- From: Richard Henderson <rth at redhat dot com>
- To: "Lynn A. Boger" <laboger at linux dot vnet dot ibm dot com>, gcc-patches at gcc dot gnu dot org, libffi-discuss at sourceware dot org, gofrontend-dev at googlegroups dot com
- Date: Thu, 06 Nov 2014 14:17:05 +0100
- Subject: Re: [PATCH 00/13] Go closures, libffi, and the static chain
- Authentication-results: sourceware.org; auth=none
- References: <1412973773-3942-1-git-send-email-rth at redhat dot com> <545A97BA dot 3030507 at linux dot vnet dot ibm dot com> <545B1C44 dot 3000306 at redhat dot com> <20141106124838 dot GJ30857 at bubble dot grove dot modra dot org> <545B7331 dot 7040500 at linux dot vnet dot ibm dot com>
On 11/06/2014 02:10 PM, Lynn A. Boger wrote:
> Aren't there cases where the static chain register is needed? How does that
> work if it could be trashed on a plt call?
No. At the moment the static chain is only used for nested functions, which
are local to the translation unit, and are therefore locally bound, and
therefore never go through the plt.
r~
- References:
- [PATCH 00/13] Go closures, libffi, and the static chain
- Re: [PATCH 00/13] Go closures, libffi, and the static chain
- Re: [PATCH 00/13] Go closures, libffi, and the static chain
- Re: [PATCH 00/13] Go closures, libffi, and the static chain
- Re: [PATCH 00/13] Go closures, libffi, and the static chain