[XLA] Attach an HloModuleConfig to HloModule, obviating the need to pass them around as a pair.

This cuts through a bunch of critical XLA APIs, but it's time... The background for this change is to make flags/options more easily pipe-able from the TF/XLA boundary deep into the XLA compiler and other components.

The situation after this CL is still not perfect; there are a number of places with chicken-egg scenarios when a module has to be constructed before a config (to register the result shape), but the situation is strictly better than before. Future CLs will clean things up even more.

PiperOrigin-RevId: 156469639

1 files changed, 4 insertions, 2 deletions

diff --git a/tensorflow/compiler/xla/service/hlo_cost_analysis_test.cc b/tensorflow/compiler/xla/service/hlo_cost_analysis_test.cc
index 22e782da27..f71ffeb887 100644
--- a/tensorflow/compiler/xla/service/hlo_cost_analysis_test.cc
+++ b/tensorflow/compiler/xla/service/hlo_cost_analysis_test.cc
@@ -126,8 +126,10 @@ class HloCostAnalysisTest : public ::testing::Test {
     auto user_computation = user_computation_status.ConsumeValueOrDie();
     VersionedComputationHandle versioned_handle =
         user_computation->GetVersionedHandle();
-    return std::move(
-        computation_tracker_.BuildHloModule(versioned_handle).ValueOrDie());
+    return std::move(computation_tracker_
+                         .BuildHloModule(versioned_handle,
+                                         /*config=*/nullptr)
+                         .ValueOrDie());
   }
 
   Client* client_;