[SYCL][L0] Remove ZeModule when program build failed

sycl/plugins/level_zero/pi_level_zero.cpp

@@ -4296,18 +4296,29 @@ pi_result piProgramBuild(pi_program Program, pi_uint32 NumDevices,
   ze_device_handle_t ZeDevice = DeviceList[0]->ZeDevice;
   ze_context_handle_t ZeContext = Program->Context->ZeContext;
   ze_module_handle_t ZeModule = nullptr;
-  ZE_CALL(zeModuleCreate, (ZeContext, ZeDevice, &ZeModuleDesc, &ZeModule,
-                           &Program->ZeBuildLog));
-
+  ze_result_t ZeResult =
+      ZE_CALL_NOCHECK(zeModuleCreate, (ZeContext, ZeDevice, &ZeModuleDesc,
+                                       &ZeModule, &Program->ZeBuildLog));
+  if (ZeResult != ZE_RESULT_SUCCESS) {
+    // We adjust pi_program below to avoid attempting to release zeModule when
+    // RT calls piProgramRelease().
+    Program->ZeModule = nullptr;
+    Program->Code.reset();
+    Program->State = _pi_program::Invalid;
+    return mapError(ZeResult);
+  }
   // The call to zeModuleCreate does not report an error if there are
   // unresolved symbols because it thinks these could be resolved later via a
   // call to zeModuleDynamicLink.  However, modules created with piProgramBuild
   // are supposed to be fully linked and ready to use.  Therefore, do an extra
   // check now for unresolved symbols.
-  ze_result_t ZeResult = checkUnresolvedSymbols(ZeModule, &Program->ZeBuildLog);
-  if (ZeResult == ZE_RESULT_ERROR_MODULE_LINK_FAILURE) {
-    return PI_BUILD_PROGRAM_FAILURE;
-  } else if (ZeResult != ZE_RESULT_SUCCESS) {
+  ZeResult = checkUnresolvedSymbols(ZeModule, &Program->ZeBuildLog);
+  if (ZeResult != ZE_RESULT_SUCCESS) {
+    // Note that the ZeModule is still allocated and will be released when
+    // the user catch the exception that RT throws.
+    // Otherwise, the user program terminates and memory leak is not a concern.
+    if (ZeResult == ZE_RESULT_ERROR_MODULE_LINK_FAILURE)
+      return PI_BUILD_PROGRAM_FAILURE;
     return mapError(ZeResult);
   }