Re: showstopper bug on x86 (Re: libffi does not follow proper ABI on ia32)

[u-xsnf@aetey.se]

On Fri, Jan 02, 2015 at 02:20:22PM -0800, Richard Henderson wrote:
> On 01/02/2015 10:56 AM, u-xsnf@aetey.se wrote:
> > Looking at the source I wonder if this has to do with the reliance
> > on the fastcall attribute, which pcc does not support.
> 
> Ah, well, that could well be.  Since fastcall is a standard Windows
> calling convention, I sort of assume every decent compiler supports it.
> 
> In which case I'm going to suggest not building libffi with pcc.
> An executable built with pcc should work with a library built with
> gcc or clang.

Oh that's too bad.

As long as C code is concerned it would be a burden to build and
eventually maintain either gcc or clang for the sole purpose to compile
libffi.

Is it hard to make libffi implementation compatible with cdecl?
The calling conventions is exactly what the library is competent about. 

If the internal use of fastcall is desirable in certain cases, then
a compile time choice between fastcall and cdecl would alleviate the
problem and make one-compiler-shops with pcc (or even something else
like tcc?) happy.

Rune