[llvm] Mips: Route ABI queries through the subtarget (PR #226667)

[LLVM Continuous Integration via llvm-commits]

llvm-ci wrote:

LLVM Buildbot has detected a new failure on builder `lldb-x86_64-win` running on `as-builder-10` while building `llvm` at step 9 "test-check-lldb-api".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/211/builds/11166

<details>
<summary>Here is the relevant piece of the build log for the reference</summary>

```
Step 9 (test-check-lldb-api) failure: Test just built components: check-lldb-api completed (failure)
******************** TEST 'lldb-api :: functionalities/breakpoint/two_hits_one_actual/TestTwoHitsOneActual.py' FAILED ********************
Script:
--
C:/Python312/python.exe C:/buildbot/as-builder-10/lldb-x86-64/llvm-project/lldb\test\API\dotest.py -u CXXFLAGS -u CFLAGS --env LLVM_LIBS_DIR=C:/buildbot/as-builder-10/lldb-x86-64/build/./lib --env LLVM_INCLUDE_DIR=C:/buildbot/as-builder-10/lldb-x86-64/build/include --env LLVM_TOOLS_DIR=C:/buildbot/as-builder-10/lldb-x86-64/build/./bin --triple x86_64-pc-windows-msvc --build-dir C:/buildbot/as-builder-10/lldb-x86-64/build/lldb-test-build --lldb-module-cache-dir C:/buildbot/as-builder-10/lldb-x86-64/build/lldb-test-build/module-cache-lldb\lldb-api --clang-module-cache-dir C:/buildbot/as-builder-10/lldb-x86-64/build/lldb-test-build/module-cache-clang\lldb-api --executable C:/buildbot/as-builder-10/lldb-x86-64/build/./bin/lldb.exe --lldb-python-dir C:\buildbot\as-builder-10\lldb-x86-64\build\lib\site-packages --compiler C:/buildbot/as-builder-10/lldb-x86-64/build/./bin/clang.exe --dsymutil C:/buildbot/as-builder-10/lldb-x86-64/build/./bin/dsymutil.exe --make C:/ninja/make.exe --llvm-tools-dir C:/buildbot/as-builder-10/lldb-x86-64/build/./bin --lldb-obj-root C:/buildbot/as-builder-10/lldb-x86-64/build/tools/lldb --lldb-libs-dir C:/buildbot/as-builder-10/lldb-x86-64/build/./lib --cmake-build-type Release --skip-category=lldb-dap --env LLDB_LAUNCH_FLAG_USE_PIPES=1 C:\buildbot\as-builder-10\lldb-x86-64\llvm-project\lldb\test\API\functionalities\breakpoint\two_hits_one_actual -p TestTwoHitsOneActual.py --timeout 600
--
Exit Code: 1

Command Output (stdout):
--
Skipping the following test categories: lldb-dap, libc++, libstdcxx, dwo, dsym, gmodules, debugserver, objc, fork, pexpect


--
Command Output (stderr):
--
FAIL: LLDB (C:\buildbot\as-builder-10\lldb-x86-64\build\bin\clang.exe-x86_64) :: test_two_hits_one_actual (TestTwoHitsOneActual.TestTwoHitsOneActual.test_two_hits_one_actual)

Log Files:

 - C:\buildbot\as-builder-10\lldb-x86-64\build\lldb-test-build\functionalities\breakpoint\two_hits_one_actual\TestTwoHitsOneActual\Failure_test_two_hits_one_actual.log

======================================================================

FAIL: test_two_hits_one_actual (TestTwoHitsOneActual.TestTwoHitsOneActual.test_two_hits_one_actual)

   There can be many tests in a test case - describe this test here.

----------------------------------------------------------------------

Traceback (most recent call last):

  File "C:\buildbot\as-builder-10\lldb-x86-64\llvm-project\lldb\packages\Python\lldbsuite\test\decorators.py", line 221, in wrapper

    return func(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "C:\buildbot\as-builder-10\lldb-x86-64\llvm-project\lldb\test\API\functionalities\breakpoint\two_hits_one_actual\TestTwoHitsOneActual.py", line 24, in test_two_hits_one_actual

    self.sample_test()

  File "C:\buildbot\as-builder-10\lldb-x86-64\llvm-project\lldb\test\API\functionalities\breakpoint\two_hits_one_actual\TestTwoHitsOneActual.py", line 66, in sample_test

    self.assertStopReason(

  File "C:\buildbot\as-builder-10\lldb-x86-64\llvm-project\lldb\packages\Python\lldbsuite\test\lldbtest.py", line 3128, in assertStopReason

    self.fail(self._formatMessage(msg, error))

AssertionError: none (1) != breakpoint (3)
...

```

</details>

https://github.com/llvm/llvm-project/pull/226667