================ @@ -290,6 +290,24 @@ _HLSL_BUILTIN_ALIAS(__builtin_hlsl_and) bool4 and(bool4 x, bool4 y); // clang-format on +//===----------------------------------------------------------------------===// +// or builtins +//===----------------------------------------------------------------------===// + +/// \fn T or(T x, T y) +/// \brief Returns the bitwise OR of the two input values, \a x and \a y. +/// \param x The first input value and y The second input value. +/// +/// \returns The logically OR a vector and retuens bool vector. + +_HLSL_BUILTIN_ALIAS(__builtin_hlsl_or) +bool or(bool, bool); +_HLSL_BUILTIN_ALIAS(__builtin_hlsl_or) +bool2 or(bool2, bool2); +_HLSL_BUILTIN_ALIAS(__builtin_hlsl_or) +bool3 or(bool3, bool3); +_HLSL_BUILTIN_ALIAS(__builtin_hlsl_or) +bool4 or(bool4, bool4); ---------------- metkarpoonam wrote:
When I initially added 'or intrinsic' to the code, 'and intrinsic' was not included, so I utilized a different function style. This resulted in the discrepancy. I am now aligning it with the 'and intrinsic' description. I have added clang format off and on comments, similar to the 'and intrinsic' comments. https://github.com/llvm/llvm-project/pull/128979 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
