From: Tom Tromey <tromey@redhat.com>
To: Timothy Wall <twall@users.sourceforge.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: libffi stdcall closures
Date: Thu, 08 Nov 2007 19:11:00 -0000 [thread overview]
Message-ID: <m3tznwmxvv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8269E7B3-A99E-42AC-9314-2613A1C26ABF@users.sf.net> (Timothy Wall's message of "Thu\, 08 Nov 2007 11\:05\:36 -0500")
>>>>> "Timothy" == Timothy Wall <twall@users.sf.net> writes:
Timothy> I'm working on a patch for win32/x86 stdcall closures to support JNA
Timothy> (http://jna.dev.java.net), a ctypes-like library for Java. I'm
Timothy> working off of a libffi snapshot from the gcc trunk.
Nice. JNA looks cool.
BTW, I think I read somewhere that you have some standalone configure
changes for libffi...? We could put those in the separate libffi
repository if that would help you. I occasionally think it would be
nice to revive the standalone libffi -- but only if there's interest.
Timothy> I've got the closure code working now, and I need some pointers on
Timothy> adding a win32-only stdcall callback test to the testsuite (or a
Timothy> general one if stdcall is supported elsewhere).
libffi uses the dejagnu 'dg' code, so you should be able to just drop
your test cases into the test suite. If the test is platform-specific
I think you can use the "target" clause to dg-do. Grep for "target"
in gcc/testsuite/**/*.c to see uses.
Tom
next prev parent reply other threads:[~2007-11-08 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 16:09 Timothy Wall
2007-11-08 19:11 ` Tom Tromey [this message]
2007-11-08 22:19 ` Timothy Wall
2007-11-09 1:07 ` Timothy Wall
2007-11-13 23:28 ` Tom Tromey
2007-11-13 23:32 ` Timothy Wall
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=m3tznwmxvv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=twall@users.sourceforge.net \
/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).