Fix IRBuilderHelper assertion when DtoDefineNakedFunction called at module scope

Use gIR->saveInsertPoint() instead of gIR->ir->saveIP() because the
latter goes through IRBuilderHelper::operator->() which asserts that
there's a valid insert block. At module scope (e.g., when compiling
naked functions in phobos), there may not be an existing insert point.

The RAII InsertPointGuard handles both null and non-null insert points
correctly, saving and restoring the builder state automatically.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: Dev VM

gen/naked.cpp

@@ -201,8 +201,11 @@ void DtoDefineNakedFunction(FuncDeclaration *fd) {
   llvm::BasicBlock *entryBB =
       llvm::BasicBlock::Create(gIR->context(), "entry", func);
 
-  // Save current insert point and switch to new function
-  llvm::IRBuilderBase::InsertPoint savedIP = gIR->ir->saveIP();
+  // Save current insert point and switch to new function.
+  // Use gIR->saveInsertPoint() instead of gIR->ir->saveIP() because the latter
+  // goes through IRBuilderHelper::operator->() which asserts that there's a
+  // valid insert block. At module scope, there may not be one yet.
+  const auto savedInsertPoint = gIR->saveInsertPoint();
   gIR->ir->SetInsertPoint(entryBB);
 
   // Clear the nakedAsm stream and collect the function body
@@ -252,8 +255,8 @@ void DtoDefineNakedFunction(FuncDeclaration *fd) {
   // Naked functions don't return normally through LLVM IR
   gIR->ir->CreateUnreachable();
 
-  // Restore insert point
-  gIR->ir->restoreIP(savedIP);
+  // The savedInsertPoint RAII guard automatically restores the insert point
+  // when it goes out of scope.
 
   // Handle DLL export on Windows
   if (global.params.dllexport ||