[RISCV][GISel] Legalize G_SADDO/G_SSUBO/G_UADDO/G_USUBO.

[topperc]

No description provided.

[github-actions]

⚠️ C/C++ code formatter, clang-format found issues in your code. ⚠️

You can test this locally with the following command:

git-clang-format --diff 3e87829a8a9ab6a5f62078c590eec09f5024f95f a31b927bbf4650fab5338878d7f9d55e3fb8bcb8 -- llvm/lib/Target/RISCV/GISel/RISCVLegalizerInfo.cpp

View the diff from clang-format here.

diff --git a/llvm/lib/Target/RISCV/GISel/RISCVLegalizerInfo.cpp b/llvm/lib/Target/RISCV/GISel/RISCVLegalizerInfo.cpp
index 562b522dfacd..2a451b3ba5e9 100644
--- a/llvm/lib/Target/RISCV/GISel/RISCVLegalizerInfo.cpp
+++ b/llvm/lib/Target/RISCV/GISel/RISCVLegalizerInfo.cpp
@@ -41,8 +41,7 @@ RISCVLegalizerInfo::RISCVLegalizerInfo(const RISCVSubtarget &ST) {
       .widenScalarToNextPow2(0)
       .clampScalar(0, s32, XLenLLT);
 
-  getActionDefinitionsBuilder(
-      {G_UADDE, G_UADDO, G_USUBE, G_USUBO}).lower();
+  getActionDefinitionsBuilder({G_UADDE, G_UADDO, G_USUBE, G_USUBO}).lower();
 
   getActionDefinitionsBuilder({G_SADDO, G_SSUBO}).minScalar(0, XLenLLT).lower();
 

[mshockwave]

code formatting here seems a little bit weird...the clang-format bot was not happy about this either

[nitinjohnraj]

LGTM