From: Tom Tromey <tromey@redhat.com>
To: "Mike Thomas" <miketh@brisbane.paradigmgeo.com>
Cc: <gcc@gcc.gnu.org>, <axiom-developer@nongnu.org>,
<maxima@mail.ma.utexas.edu>, <acl2@lists.cc.utexas.edu>,
<gcl-devel@gnu.org>
Subject: Re: [Gcl-devel] Re: portable cdecl 'elliptic' function calls
Date: Fri, 01 Aug 2003 01:22:00 -0000 [thread overview]
Message-ID: <87zniu2p38.fsf@fleche.redhat.com> (raw)
In-Reply-To: <MFEIIPBIPCKFPICNGIJNOENDDIAA.miketh@brisbane.paradigmgeo.com>
>>>>> "Mike" == Mike Thomas <miketh@brisbane.paradigmgeo.com> writes:
Mike> The gcc source seems to imply it works on Windows but some docs
Mike> I've read on the web don't list Windows as a target platform for
Mike> libffi. (Never built gcc so can't say which.)
libffi works fine on Windows. You can easily find out where it works
by looking in gcc/libffi/configure.in. There is a big case statement
that sets up the build for all the working platforms.
Things are a little different if you use the closure API. Then you
have to look in gcc/libffi/include/ffi.h.in to see what platforms
define FFI_CLOSURES.
The "normal" API works on more platforms than the closure API. I
think libffi works on all the Debian architectures except HPPA.
Nobody has ever done that port.
Tom
WARNING: multiple messages have this Message-ID
From: tromey@redhat.com (Tom Tromey)
To: gcc@gcc.gnu.org
Subject: Re: [Gcl-devel] Re: portable cdecl 'elliptic' function calls
Date: Fri, 01 Aug 2003 02:29:00 -0000 [thread overview]
Message-ID: <87zniu2p38.fsf@fleche.redhat.com> (raw)
Message-ID: <20030801022900.JutjdHohZsTkh0pNHUTTshJ7GUwg51pI3Hgiy1xAFg0@z> (raw)
In-Reply-To: <MFEIIPBIPCKFPICNGIJNOENDDIAA.miketh@brisbane.paradigmgeo.com>
>>>>> "Mike" == Mike Thomas <miketh@brisbane.paradigmgeo.com> writes:
Mike> The gcc source seems to imply it works on Windows but some docs
Mike> I've read on the web don't list Windows as a target platform for
Mike> libffi. (Never built gcc so can't say which.)
libffi works fine on Windows. You can easily find out where it works
by looking in gcc/libffi/configure.in. There is a big case statement
that sets up the build for all the working platforms.
Things are a little different if you use the closure API. Then you
have to look in gcc/libffi/include/ffi.h.in to see what platforms
define FFI_CLOSURES.
The "normal" API works on more platforms than the closure API. I
think libffi works on all the Debian architectures except HPPA.
Nobody has ever done that port.
Tom
next prev parent reply other threads:[~2003-08-01 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 22:48 Camm Maguire
2003-07-29 9:52 ` Fergus Henderson
2003-07-31 2:40 ` Camm Maguire
2003-07-31 6:42 ` [Gcl-devel] " Mike Thomas
2003-07-31 14:53 ` Fergus Henderson
2003-08-01 1:22 ` Tom Tromey [this message]
2003-08-01 2:29 ` Tom Tromey
2003-07-29 11:37 ` [Axiom-developer] " Arthur Norman
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=87zniu2p38.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=acl2@lists.cc.utexas.edu \
--cc=axiom-developer@nongnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gcl-devel@gnu.org \
--cc=maxima@mail.ma.utexas.edu \
--cc=miketh@brisbane.paradigmgeo.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).