[flang-commits] [flang] [draft][flang] Query backend support for quad-precision compilation decision (PR #182230)

[via flang-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 origin/main...HEAD flang/test/lit.cfg.py
``````````

:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:

</details>

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

``````````diff
--- lit.cfg.py	2026-03-05 07:58:02.000000 +0000
+++ lit.cfg.py	2026-03-05 08:00:01.508550 +0000
@@ -203,10 +203,11 @@
     # project or runtime.
     if config.openmp_module_dir:
         openmp_flags_substitution += f" -J {config.openmp_module_dir}"
 config.substitutions.append(("%openmp_flags", openmp_flags_substitution))
 
+
 def flang_supports_f128():
     flang_exe = lit.util.which("flang", config.clang_tools_dir)
 
     if not flang_exe:
         return False
@@ -226,11 +227,15 @@
         return True
 
 # Add features and substitutions to test F128 math support.
 # %f128-lib substitution may be used to generate check prefixes
 # for LIT tests checking for F128 library support.
-if config.flang_runtime_f128_math_lib or config.have_ldbl_mant_dig_113 or flang_supports_f128():
+if (
+    config.flang_runtime_f128_math_lib
+    or config.have_ldbl_mant_dig_113
+    or flang_supports_f128()
+):
     config.available_features.add("flang-supports-f128-math")
 if config.flang_runtime_f128_math_lib:
     config.available_features.add(
         "flang-f128-math-lib-" + config.flang_runtime_f128_math_lib
     )

``````````

</details>


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