[libc-commits] [clang] [libc] [libcxx] [clang][X86] Emit AVX level mismatch psABI warnings on function definitions (PR #199091)

via libc-commits libc-commits at lists.llvm.org
Thu May 21 11:51:34 PDT 2026


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 libcxx/utils/libcxx/test/params.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
--- params.py	2026-05-21 18:45:53.000000 +0000
+++ params.py	2026-05-21 18:51:01.908911 +0000
@@ -73,11 +73,10 @@
     # This doesn't make sense in real code, but we have to test it because the standard requires us to not break
     "-Wno-self-move",
 
     # We're not annotating all the APIs, since that's a lot of annotations compared to how many we actually care about
     "-Wno-nullability-completeness",
-
     # Adding this for now to get the build to pass but needs more detailed review
     "-Wno-psabi",
 
     # Technically not a warning flag, but might as well be:
     "-flax-vector-conversions=none",

``````````

</details>


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


More information about the libc-commits mailing list