[clang] [clang] Allow __attribute__((swiftcall)) on all targets (PR #71986)

s-barannikov wrote: I think the choice whether or not to support Swift calling convention should be made by individual targets without providing "safe" default. As pointed out in the linked PR, supporting Swift CC is not only about enabling the attribute support -- backend also needs

[clang] [clang] Allow __attribute__((swiftcall)) on all targets (PR #71986)

github-actions[bot] wrote: :warning: C/C++ code formatter, clang-format found issues in your code. :warning: You can test this locally with the following command: ``bash git-clang-format --diff 199fc973ced20016b04ba540cf63a1d4914fa513 d2df2830b4417c0ecc9690c4092053bf465a5d44 --

[clang] [clang] Allow __attribute__((swiftcall)) on all targets (PR #71986)

llvmbot wrote: @llvm/pr-subscribers-clang Author: Kuba (Brecka) Mracek (kubamracek) Changes With Embedded Swift, https://forums.swift.org/t/embedded-swift/67057;, it becomes possible and useful to produce Swift code for a whole range of CPU targets. This change allows using the

[clang] [clang] Allow __attribute__((swiftcall)) on all targets (PR #71986)

https://github.com/kubamracek created https://github.com/llvm/llvm-project/pull/71986 With Embedded Swift, , it becomes possible and useful to produce Swift code for a whole range of CPU targets. This change allows using the 'swiftcall' and