github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {clang-format}-->
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
git-clang-format --diff origin/main HEAD --extensions h --
libc/src/__support/FPUtil/aarch64/fenv_darwin_impl.h --diff_from_common_commit
``````````
: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 clang-format here.
</summary>
``````````diff
diff --git a/libc/src/__support/FPUtil/aarch64/fenv_darwin_impl.h
b/libc/src/__support/FPUtil/aarch64/fenv_darwin_impl.h
index 595955518..3985bf061 100644
--- a/libc/src/__support/FPUtil/aarch64/fenv_darwin_impl.h
+++ b/libc/src/__support/FPUtil/aarch64/fenv_darwin_impl.h
@@ -25,9 +25,9 @@
#include "src/__support/FPUtil/FPBits.h"
// libc's <fenv.h> spells the denormal/flush-to-zero exception FE_DENORM, while
-// the system (Apple) <fenv.h> used in an overlay build spells it
FE_FLUSHTOZERO.
-// Provide the latter as an alias in a full build so the code below uses a
single
-// name.
+// the system (Apple) <fenv.h> used in an overlay build spells it
+// FE_FLUSHTOZERO. Provide the latter as an alias in a full build so the code
+// below uses a single name.
#ifndef FE_FLUSHTOZERO
#define FE_FLUSHTOZERO FE_DENORM
#endif
``````````
</details>
https://github.com/llvm/llvm-project/pull/205016
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
