Fix register names in restricted configuration

Even in the restricted config, we can still end up having to print
certain non-allocatable registers, e.g. if required by a FIXED_REGISTER
policy. The names list needs to contain all general register names.

Change-Id: I70104d6ba02779437de14eca01dc1900c159aa6a
Reviewed-on: https://chromium-review.googlesource.com/1184846Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#55308}

src/register-configuration.cc

@@ -231,8 +231,8 @@ class RestrictedRegisterConfiguration : public RegisterConfiguration {
             allocatable_general_register_codes.get(),
             get_allocatable_double_codes(),
             kSimpleFPAliasing ? AliasingKind::OVERLAP : AliasingKind::COMBINE,
-            allocatable_general_register_names.get(), kFloatRegisterNames,
-            kDoubleRegisterNames, kSimd128RegisterNames),
+            kGeneralRegisterNames, kFloatRegisterNames, kDoubleRegisterNames,
+            kSimd128RegisterNames),
         allocatable_general_register_codes_(
             std::move(allocatable_general_register_codes)),
         allocatable_general_register_names_(