On May 7 00:59, Kai Tietz wrote: > Yes, magic wording here is that compiler accepts it and ignores it. > So it means not in headers.
Sorry, but I don't get this. So per MSDN, x64 and ARM are identical with respect to __stdcall. If so, why is it the right thing to #define __stdcall for x64, but the same is not right for ARM?!? I fail to see the difference. Corinna > > Cheers > Kai > Am 07.05.2014 00:51 schrieb "Yaakov (Cygwin/X)" < > [email protected]>: > > > On 2014-05-06 16:37, Kai Tietz wrote: > > > 2014-05-06 21:15 GMT+02:00 André Hentschel: > > >> Am 06.05.2014 21:01, schrieb Yaakov (Cygwin/X): > > >>> On 2014-05-05 16:32, André Hentschel wrote: > > >>>> Am 05.05.2014 23:29, schrieb André Hentschel: > > >>>>> Please review, i'll commit it. > > >>>> > > >>>> Again the right patch attached now, it's getting late, sorry. > > >>> > > >>> Since stdcall isn't used on x64 either, wouldn't it make more sense to > > >>> just do the following in _mingw.h: > > >>> > > >>> /* C/C++ specific language defines. */ > > >>> -#ifdef _WIN64 > > >>> +#if defined(_WIN64) || defined(_ARM_) > > >>> #ifdef __stdcall > > >>> #undef __stdcall > > >>> #endif > > >>> #define __stdcall > > >>> #endif > > >>> > > >> > > >> Looks like that should work, be free to send a patch as this should > > help with the remaining use of __stdcall in functions > > > > > > No, for x64 there is still the function-attribute. It has no mean in > > > terms of different calling-convention in ABI. Nevertheless it is used > > > (and need to be handled) by diagnostics. > > > > According to MSDN, x64 and ARM are identical wrt __stdcall: > > > > [1] http://msdn.microsoft.com/en-us/library/zxk0tw93.aspx > > > > > > Yaakov > > Cygwin Ports > > > > > > > > ------------------------------------------------------------------------------ > > Is your legacy SCM system holding you back? Join Perforce May 7 to find > > out: > > • 3 signs your SCM is hindering your productivity > > • Requirements for releasing software faster > > • Expert tips and advice for migrating your SCM now > > http://p.sf.net/sfu/perforce > > _______________________________________________ > > Mingw-w64-public mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Mingw-w64-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
pgpAkzxf9x3mw.pgp
Description: PGP signature
------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
