From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: Mike Thomas <miketh@brisbane.paradigmgeo.com>
Cc: Camm Maguire <camm@enhanced.com>,
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: Thu, 31 Jul 2003 14:53:00 -0000 [thread overview]
Message-ID: <20030731135251.GA29018@ceres.cs.mu.oz.au> (raw)
In-Reply-To: <MFEIIPBIPCKFPICNGIJNOENDDIAA.miketh@brisbane.paradigmgeo.com>
On 31-Jul-2003, Mike Thomas <miketh@brisbane.paradigmgeo.com> wrote:
> Fergus, did you use it [libffi] in the Cygwin port of Mercury?
No.
Camm Maguire <camm@enhanced.com> wrote:
> | Greetings, and thank you for this tip! I now think I see how to do
> | this in GCL, and would like to build in dependency on libffi. Is this
> | available on everyone's systems? I'm assuming its packaged at least
> | everywhere gcc is available. What about solaris, Mac OS X?
You should not assume that libffi is implemented everywhere that gcc is
available. The reason that libffi is included in the GCC distribution
is, I think, because it is used by the Java interpreter. That is a lot
less widely ported than the GNU C compiler, I would imagine.
The libffi implementation is by its nature not portable;
its implementation depends on the platform's calling convention.
However, the interface is portable, and by using libffi,
the work of implementing this interface for a bunch of different
calling conventions can be shared between all the different
projects that need this functionality.
The difficulty of porting libffi to a different OS will depend on
whether that OS uses the same calling convention as one that libffi
already supports. If so, as is the case with Cygwin, then it should
be very little work. If not, it might be a lot of work.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
next prev parent reply other threads:[~2003-07-31 13:53 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 [this message]
2003-08-01 1:22 ` Tom Tromey
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=20030731135251.GA29018@ceres.cs.mu.oz.au \
--to=fjh@cs.mu.oz.au \
--cc=acl2@lists.cc.utexas.edu \
--cc=axiom-developer@nongnu.org \
--cc=camm@enhanced.com \
--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).