https://github.com/AtariDreams updated
https://github.com/llvm/llvm-project/pull/82721
>From 815f9333db0cec9a1db87fd4c3af90097520edc6 Mon Sep 17 00:00:00 2001
From: Rose <83477269+ataridre...@users.noreply.github.com>
Date: Thu, 22 Feb 2024 20:50:48 -0500
Subject: [PATCH] [NFC] Fix formatting so CI can continue
These keep tripping up the build bots for clang and preventing testing on libc
to go forward.
---
clang/docs/HLSL/ExpectedDifferences.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/clang/docs/HLSL/ExpectedDifferences.rst
b/clang/docs/HLSL/ExpectedDifferences.rst
index 60001b22dc7920..d1b6010f10f43a 100644
--- a/clang/docs/HLSL/ExpectedDifferences.rst
+++ b/clang/docs/HLSL/ExpectedDifferences.rst
@@ -93,7 +93,7 @@ behavior between Clang and DXC. Some examples include:
fma(X, Y, Z); // DXC: Fails to resolve no known conversion from float to
double.
// Clang: Resolves to fma(double,double,double).
#endif
-
+
double D = dot(A, B); // DXC: Resolves to dot(double3, double3), fails
DXIL Validation.
// FXC: Expands to compute double dot product with
fmul/fadd
// Clang: Resolves to dot(float3, float3), emits
conversion warnings.
@@ -102,7 +102,7 @@ behavior between Clang and DXC. Some examples include:
.. note::
- In Clang, a conscious decision was made to exclude the
``dot(vector<double,N>, vector<double,N>)``
+ In Clang, a conscious decision was made to exclude the
``dot(vector<double,N>, vector<double,N>)``
overload and allow overload resolution to resolve the
``vector<float,N>`` overload. This approach provides ``-Wconversion``
diagnostic notifying the user of the conversion rather than silently altering
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
