-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mlir] tblgen no member named 'getValue' in 'mlir::OptionalParseResult' #63072
Comments
@llvm/issue-subscribers-mlir |
I believe this:
should mlir::Type() .
|
Thanks! Fixed in a6a7a1b |
I have the same issue, when trying to make my dialect extensible (let Manually going in the tblgen-generated if (::mlir::succeeded(parseResult.getValue())) to if (::mlir::succeeded(parseResult.value())) solves the issue. Could somebody with commit privileges change this here, @joker-eph perhaps? I don't know the proper process for contributing to LLVM and currently haven't got the time to figure it out. Also, I think a more thorough test of extensible dialects ( |
The TestDialect is extensible, but unfortunately this particular combination also requires |
/cherry-pick 87a1421 |
/branch llvm/llvm-project-release-prs/issue63072 |
Because of another breaking change my project doesn't build completely (my last rebuild was only 12 days ago, sometimes this development pace is a bit exhausting ^^), but the MLIR dialect library does build with |
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
…ptionalParseResult' Fix llvm#63072
llvm-project/mlir/tools/mlir-tblgen/AttrOrTypeDefGen.cpp
Line 738 in fb447e7
Thanks and follow up issue :-(
The text was updated successfully, but these errors were encountered: