From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24188 invoked by alias); 8 Nov 2007 18:15:35 -0000 Received: (qmail 24179 invoked by uid 22791); 8 Nov 2007 18:15:35 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 08 Nov 2007 18:15:33 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lA8IFVEo016055; Thu, 8 Nov 2007 13:15:31 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lA8IFUkA005391; Thu, 8 Nov 2007 13:15:30 -0500 Received: from opsy.redhat.com (ton.yyz.redhat.com [10.15.16.15]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lA8IFNDI014322; Thu, 8 Nov 2007 13:15:23 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 46F32378256; Thu, 8 Nov 2007 10:48:36 -0700 (MST) To: Timothy Wall Cc: gcc-patches@gcc.gnu.org Subject: Re: libffi stdcall closures References: <8269E7B3-A99E-42AC-9314-2613A1C26ABF@users.sf.net> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Thu, 08 Nov 2007 19:11:00 -0000 In-Reply-To: <8269E7B3-A99E-42AC-9314-2613A1C26ABF@users.sf.net> (Timothy Wall's message of "Thu\, 08 Nov 2007 11\:05\:36 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.990 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-11/txt/msg00454.txt.bz2 >>>>> "Timothy" == Timothy Wall 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