[clang] [clang] Use TargetInfo to decide Mangling for C (PR #129920)

2025-03-05 Thread LLVM Continuous Integration via cfe-commits
llvm-ci wrote: LLVM Buildbot has detected a new failure on builder `llvm-clang-aarch64-darwin` running on `doug-worker-5` while building `clang` at step 6 "test-build-unified-tree-check-all". Full details are available at: https://lab.llvm.org/buildbot/#/builders/190/builds/15781 Here is th

[clang] [clang] Use TargetInfo to decide Mangling for C (PR #129920)

2025-03-05 Thread via cfe-commits
https://github.com/Prabhuk closed https://github.com/llvm/llvm-project/pull/129920 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [clang] Use TargetInfo to decide Mangling for C (PR #129920)

2025-03-05 Thread Reid Kleckner via cfe-commits
https://github.com/rnk approved this pull request. Thanks, I spent a while thinking if this was correct, and then convincing myself that we ignore the relevant calling conventions on the appropriate platforms (we ignore `__fastcall` on x64 and ignore `__vectorcall` on Win ARM). https://github.

[clang] [clang] Use TargetInfo to decide Mangling for C (PR #129920)

2025-03-05 Thread via cfe-commits
llvmbot wrote: @llvm/pr-subscribers-clang Author: Prabhuk (Prabhuk) Changes Instead of hardcoding the decision on what mangling scheme to use based on targets, use TargetInfo to make the decision. --- Full diff: https://github.com/llvm/llvm-project/pull/129920.diff 4 Files Affected: -

[clang] [clang] Use TargetInfo to decide Mangling for C (PR #129920)

2025-03-05 Thread via cfe-commits
https://github.com/Prabhuk created https://github.com/llvm/llvm-project/pull/129920 Instead of hardcoding the decision on what mangling scheme to use based on targets, use TargetInfo to make the decision. >From 50204fcef930b215c9494b92b8c54a19d3821d5b Mon Sep 17 00:00:00 2001 From: prabhukr D