Allow graceful handling of cpuinfo init failure

Summary: Don't fatally assert when cpuinfo_initialize fails. This can happen in rare cases on weird hardware. This change instead logs an error and allows execution to continue without the threadpool. XNNPACK can't run, but it at least will allow graceful fallback at the application level.

Reviewed By: digantdesai

Differential Revision: D74604740

Author: GregoryComer

extension/threadpool/threadpool.cpp

@@ -96,7 +96,11 @@ void ThreadPool::run(
 // get_threadpool is not thread safe due to leak_corrupted_threadpool
 // Make this part threadsafe: TODO(kimishpatel)
 ThreadPool* get_threadpool() {
-  ET_CHECK_MSG(cpuinfo_initialize(), "cpuinfo initialization failed");
+  if (!cpuinfo_initialize()) {
+    ET_LOG(Error, "cpuinfo initialization failed");
+    return nullptr; // NOLINT(facebook-hte-NullableReturn)
+  }
+
   int num_threads = cpuinfo_get_processors_count();
   /*
    * For llvm-tsan, holding limit for the number of locks for a single thread