[clang][bytecode][NFC] Check for custom typechecking in call cleanup

[tbaederr]

The comment already explains that this is only true for some builtin functions. This also brings the time it takes me to run the builtin-functions.cpp test locally from 50s down to 47s.

[llvmbot]

@llvm/pr-subscribers-clang

Author: Timm Baeder (tbaederr)

Changes

The comment already explains that this is only true for some builtin functions. This also brings the time it takes me to run the builtin-functions.cpp test locally from 50s down to 47s.

---

Full diff: https://github.com/llvm/llvm-project/pull/106826.diff

1 Files Affected:

• (modified) clang/lib/AST/ByteCode/Interp.cpp (+2-1)

diff --git a/clang/lib/AST/ByteCode/Interp.cpp b/clang/lib/AST/ByteCode/Interp.cpp
index 42012767c22332..c4f76a3cc03aae 100644
--- a/clang/lib/AST/ByteCode/Interp.cpp
+++ b/clang/lib/AST/ByteCode/Interp.cpp
@@ -226,7 +226,8 @@ void cleanupAfterFunctionCall(InterpState &S, CodePtr OpPC) {
 
   // Some builtin functions require us to only look at the call site, since
   // the classified parameter types do not match.
-  if (CurFunc->isBuiltin()) {
+  if (unsigned BID = CurFunc->getBuiltinID();
+      BID && S.getASTContext().BuiltinInfo.hasCustomTypechecking(BID)) {
     const auto *CE =
         cast<CallExpr>(S.Current->Caller->getExpr(S.Current->getRetPC()));
     for (int32_t I = CE->getNumArgs() - 1; I >= 0; --I) {