This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: closures support on ARM
- From: Tom Tromey <tromey at redhat dot com>
- To: Kirill Kononenko <kirill dot kononenko at gmail dot com>
- Cc: libffi-discuss at sources dot redhat dot com
- Date: 07 Sep 2005 12:23:10 -0600
- Subject: Re: closures support on ARM
- References: <b21f6d8e050904111859800a8e@mail.gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Kirill" == Kirill Kononenko <kirill.kononenko@gmail.com> writes:
Kirill> Finally, we found that the reason is that libffi doesn't
Kirill> support FFI_CLOSURES.
Kirill> I would like to know if you could implement FFI_CLOSURES
Kirill> support for ARM? I could try to implement this support too. I
Kirill> have documentation like the ARM Architecture Reference
Kirill> Manual. Could you give me the documentation and other info
Kirill> using which I could try to implement this support?
Kirill> I don't know how difficult it might be to implement FFI_CLOSURES
Kirill> support on ARM, so could you tell about this too?
I am far from a libffi expert -- I've never done a libffi port of any
kind. But, I didn't want your message to go unanswered.
AIUI to do a port of the closures code, you have to understand the
target's ABI and write some assembly code to handle converting the
incoming arguments into the form libffi exports. Maybe the simplest
way to go about this is to read and understand one of the other ports.
Tom