Remove RegisterAllocator::Strategy

It has been obsolete since graph color was removed.

Bug: 281793697
Test: art/test/testrunner/testrunner.py --host --64 --optimizing -b
Test: m test-art-host-gtest
Change-Id: I8b42b0fe39a8601da7aa1288a8581ab8b4742614

1 files changed, 0 insertions, 7 deletions

diff --git a/compiler/driver/compiler_options.h b/compiler/driver/compiler_options.h
index 6b3e26fc70..abdb01b372 100644
--- a/compiler/driver/compiler_options.h
+++ b/compiler/driver/compiler_options.h
@@ -326,10 +326,6 @@ class CompilerOptions final {
     return deduplicate_code_;
   }
 
-  RegisterAllocator::Strategy GetRegisterAllocationStrategy() const {
-    return register_allocation_strategy_;
-  }
-
   const std::vector<std::string>* GetPassesToRun() const {
     return passes_to_run_;
   }
@@ -383,7 +379,6 @@ class CompilerOptions final {
 
  private:
   EXPORT bool ParseDumpInitFailures(const std::string& option, std::string* error_msg);
-  EXPORT bool ParseRegisterAllocationStrategy(const std::string& option, std::string* error_msg);
 
   CompilerFilter::Filter compiler_filter_;
   size_t huge_method_threshold_;
@@ -477,8 +472,6 @@ class CompilerOptions final {
   // Maximum solid block size in the generated image.
   uint32_t max_image_block_size_;
 
-  RegisterAllocator::Strategy register_allocation_strategy_;
-
   // If not null, specifies optimization passes which will be run instead of defaults.
   // Note that passes_to_run_ is not checked for correctness and providing an incorrect
   // list of passes can lead to unexpected compiler behaviour. This is caused by dependencies