[CIR] Fix problem with phantom function arguments

There was a problem introduced today where sometimes the CIR for functions
with no arguments would be generated with phantom arguments. This was
causing intermittent test failures.

The problem appears to have been that we were using two different Profile
implementations to generate the FoldingSetNodeID for CIRGenFunctionInfo
so occaissionally when we tried to look for a pre-existing entry for
a function with no arguments it would incorrectly match a
CIRGenFunctionInfo entry that had arguments.

To prevent this from happening again, I rewrote one of the two Profile
functions to call the other.

Author: andykaylor

clang/lib/CIR/CodeGen/CIRGenFunctionInfo.h

@@ -112,8 +112,16 @@ class CIRGenFunctionInfo final
 
   // NOLINTNEXTLINE(readability-identifier-naming)
   void Profile(llvm::FoldingSetNodeID &id) {
-    id.AddBoolean(required.getOpaqueData());
-    getReturnType().Profile(id);
+    // It's unfortunate that we are looping over the arguments twice (here and
+    // in the static Profile function we call from here), but if the Profile
+    // functions get out of sync, we can end up with incorrect function
+    // signatures, and we don't have the argument types in the format that the
+    // static Profile function requires.
+    llvm::SmallVector<CanQualType, 16> argTypes;
+    for (const ArgInfo &argInfo : arguments())
+      argTypes.push_back(argInfo.type);
+
+    Profile(id, required, getReturnType(), argTypes);
   }
 
   llvm::ArrayRef<ArgInfo> arguments() const {