This is similar to what's done on arm and x86_64, where these calling conventions are silently ignored, as in SVN r245076 (D12034).
Details
Diff Detail
Event Timeline
lib/Basic/Targets/AArch64.cpp | ||
---|---|---|
466–467 | Do they really ignore fastcall and vectorcall on arm64? I assume thiscall and stdcall are all over various Win SDK headers, so they need to be ignored for compatibility, but I've never seen public documented APIs using __vectorcall. The STL ifdefs out those overloads, right? |
lib/Basic/Targets/AArch64.cpp | ||
---|---|---|
466–467 |
Ping @mgrang, can you check the above with MSVC? I'd like to move forward with this in one form or another.
Yes, I checked with MSVC for ARM64 and it compiles without any warnings.
cl foo.c -c /W3 Microsoft (R) C/C++ Optimizing Compiler for ARM64 Copyright (C) Microsoft Corporation. All rights reserved. foo.c
Do they really ignore fastcall and vectorcall on arm64?
I assume thiscall and stdcall are all over various Win SDK headers, so they need to be ignored for compatibility, but I've never seen public documented APIs using __vectorcall. The STL ifdefs out those overloads, right?