[clang] [CIR] Implement global array dtor support (PR #169070)

[Erich Keane via cfe-commits]

================
@@ -693,6 +696,101 @@ void LoweringPreparePass::lowerUnaryOp(cir::UnaryOp op) {
   op.erase();
 }
 
+cir::FuncOp LoweringPreparePass::getOrCreateDtorFunc(CIRBaseBuilderTy &builder,
+                                                     cir::GlobalOp op,
+                                                     mlir::Region &dtorRegion,
+                                                     cir::CallOp &dtorCall) {
+  assert(!cir::MissingFeatures::astVarDeclInterface());
+  assert(!cir::MissingFeatures::opGlobalThreadLocal());
+
+  cir::VoidType voidTy = builder.getVoidTy();
+  auto voidPtrTy = cir::PointerType::get(voidTy);
+
+  // Look for operations in dtorBlock
+  mlir::Block &dtorBlock = dtorRegion.front();
+
+  // The first operation should be a get_global to retrieve the address
+  // of the global variable we're destroying.
+  auto opIt = dtorBlock.getOperations().begin();
+  cir::GetGlobalOp ggop = mlir::cast<cir::GetGlobalOp>(*opIt);
+
+  // The simple case is just a call to a destructor, like this:
+  //
+  //   %0 = cir.get_global %globalS : !cir.ptr<!rec_S>
----------------
erichkeane wrote:

Oh yeah, that seems sensible.  Just seemed a little odd.  I guess I was envisioning some sort of 'get-self' type thing... 

I guess I see what you mean, any call (in the non-array case) would need that.  The way I could think of would be to have the block take an argument that has that value (like `array.dtor`'s `bb0`).

But I can see that being fine in a followup/with a FIXME put somewhere.

https://github.com/llvm/llvm-project/pull/169070