I think we should ignore that somebody uses -mno-sse for x64. First
this would be clearly an ABI-breakage, due SSE is mandatory in
calling-convention.
Agreed.
TIL: x64 uses SSE features for passing parameters (for example using
XMM0 for floating point).
There is a similar question for
2013/6/4 dw limegreenso...@yahoo.com:
I think option #3 is that one I prefer too. Just one thing about
SSE-instruction. For 64-bit we can assume that SSE has to be present
in any case. Just for 32-bit we should check in headers for the
__SSE__ macro, and in the intrinsic-function
2013/6/3 dw limegreenso...@yahoo.com:
So, a question about __faststorefence. The current implementation in
winnt.h is incorrect. I have 3 alternates to propose, and which one is
best depends on the goals of the mingw-w64 project. One approach is just
do what MSVC does. However, there's
I think option #3 is that one I prefer too. Just one thing about
SSE-instruction. For 64-bit we can assume that SSE has to be present
in any case. Just for 32-bit we should check in headers for the
__SSE__ macro, and in the intrinsic-function (none-inline) we should
default to none-SSE
So, a question about __faststorefence. The current implementation in
winnt.h is incorrect. I have 3 alternates to propose, and which one is
best depends on the goals of the mingw-w64 project. One approach is
just do what MSVC does. However, there's also something to be said
for generate
