[llvm] It is really the byte order of the target that matters (PR #107915)

[via llvm-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r 6f8d2781f604cfcf9ea6facecc0bea8e4d682e1e...53e069a8579028993b266621cfaf1605b81bbdd3 llvm/test/lit.cfg.py
``````````

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- lit.cfg.py	2024-09-09 21:11:07.000000 +0000
+++ lit.cfg.py	2024-09-09 21:17:49.996137 +0000
@@ -361,11 +361,14 @@
 if config.host_ldflags.find("-m32") < 0 and any(
     config.llvm_host_triple.startswith(x) for x in known_arches
 ):
     config.available_features.add("llvm-64-bits")
 
-if re.match(r"(aarch64_be|arc|armeb|bpfeb|lanai|m68k|mips|mips64|powerpc|powerpc64|sparc|sparcv9|s390x|s390|tce|thumbeb)-.*", config.target_triple):
+if re.match(
+    r"(aarch64_be|arc|armeb|bpfeb|lanai|m68k|mips|mips64|powerpc|powerpc64|sparc|sparcv9|s390x|s390|tce|thumbeb)-.*",
+    config.target_triple,
+):
     config.available_features.add("target-byteorder-big-endian")
 else:
     config.available_features.add("target-byteorder-little-endian")
 
 if sys.platform in ["win32"]:

``````````

</details>


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