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


>>>>> "Paolo" == Paolo Bonzini <bonzini@gnu.org> writes:

>> The intent here is to move the bulk of the runtime configury into per-cpu
>> header files instead of ifdefs in ffi.h.  It also cleans up some namespace
>> issues, such that nothing that doesn't start with FFI_ or ffi_ is seen in
>> the header files.

This seems like a nice idea.

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?

Tom


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