your patch broke darwin libffi

[Bryce McKinlay]

David Edelsohn wrote:

>	No other libffi port has the ABI name different from the
>ffi_call_* name.
>
The only reason I can see for having a unique name would be to allow one 
build of libffi to support more than one ABI simultaniously. libffi was 
obviously designed with this in mind (witness the "switch (cif->abi)" in 
ffi_call), but in practice I don't think it works. You can't call a SYSV 
function from darwin for example because the C part of the 
implementation is also different. Is supporting multiple ABIs in libffi 
really possible, and if so, is it useful?

regards

Bryce.