[clang] [CIR][NFC] Fix incorrect function names in assert messages (PR #174334)
via cfe-commits
cfe-commits at lists.llvm.org
Sun Jan 4 06:58:09 PST 2026
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 -- clang/lib/CIR/CodeGen/CIRGenFunction.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/clang/lib/CIR/CodeGen/CIRGenFunction.h b/clang/lib/CIR/CodeGen/CIRGenFunction.h
index 25d95e300..49ebccc22 100644
--- a/clang/lib/CIR/CodeGen/CIRGenFunction.h
+++ b/clang/lib/CIR/CodeGen/CIRGenFunction.h
@@ -218,8 +218,7 @@ public:
/// constant op.
static int64_t getZExtIntValueFromConstOp(mlir::Value val) {
auto constOp = val.getDefiningOp<cir::ConstantOp>();
- assert(constOp &&
- "getZExtIntValueFromConstOp call with non ConstantOp");
+ assert(constOp && "getZExtIntValueFromConstOp call with non ConstantOp");
return constOp.getIntValue().getZExtValue();
}
``````````
</details>
https://github.com/llvm/llvm-project/pull/174334
More information about the cfe-commits
mailing list