This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFA/RFT] libffi reorg

From: "Paolo Bonzini" <bonzini at gnu dot org>
To: <tromey at redhat dot com>
Cc: <gcc-patches at gcc dot gnu dot org>
Date: Fri, 19 Sep 2003 22:28:25 +0200
Subject: Re: [RFA/RFT] libffi reorg
References: <1058195670.3331.25.camel@escape><003401c37e9b$de5fb230$e314623e@philo> <87smmslpn4.fsf@fleche.redhat.com>

> However, I've also wanted a way for libffi to tell client programs
> about its local configury.  For instance, right now in
> libjava/configure.host we have code that knows whether a given
> platform supports the closure API (or libffi at all).  But why should
> we do that, when libffi already knows this?  I wish we could just
> unconditionally include some libffi header and use some exported
> define to decide what to do.  Any thoughts on that?

FFI_CLOSURES is exported (through ffitarget.h) by ffi.h for example.

Paolo

References:
- [RFA/RFT] libffi reorg
  - From: Paolo Bonzini
- Re: [RFA/RFT] libffi reorg
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]