[Mlir-commits] [mlir] [mlir][IR] Improve error message when parsing incorrect type (PR #134984)
Jeremy Kun
llvmlistbot at llvm.org
Wed Apr 9 06:29:02 PDT 2025
================
@@ -129,7 +129,7 @@ func.func private @test_verifier_fails() -> () attributes {
// -----
func.func private @test_attr_with_type_failed_to_parse_type() -> () attributes {
- // expected-error at +2 {{invalid kind of type specified}}
+ // expected-error at +2 {{invalid kind of type specified: expected builtin.integer, but found 'vector<4xi32>}}
----------------
j2kun wrote:
It's weird to me that some of the types printed have a leading single quote, some have wrapping single quotes. I suspect that is an issue with the consistency of their printers and not this PR, but I also can't find where in the codebase these single quotes are even emitted. Is it possible you just left off the trailing single quote in your expectation?
https://github.com/llvm/llvm-project/pull/134984
More information about the Mlir-commits
mailing list