Calling convention optimizations can probably be done during
whole program optimization, which 1) usable for
computation-intensive applications anyway, 2) guarantees
invisibility of those fastcall functions to external code so
there's no incompatibility.
- A new calling convention in VS2013 bearophile
- Re: A new calling convention in VS2013 Iain Buclaw
- Re: A new calling convention in VS2013 Benjamin Thaut
- Re: A new calling convention in VS2013 bearophile
- Re: A new calling convention in VS2013 Kagamin
- Re: A new calling convention in VS2013 bearophile
- Re: A new calling convention in VS2013 Benjamin Thaut
- Re: A new calling convention in VS2013 bearophile
- Re: A new calling convention in VS2013 bearophile