Skip to content
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

Closed
tschuett opened this issue Jun 2, 2023 · 10 comments
Closed

Comments

@tschuett
Copy link

tschuett commented Jun 2, 2023

if (::mlir::succeeded(parseResult.getValue()))

: error: no member named 'getValue' in 'mlir::OptionalParseResult'
      if (::mlir::succeeded(parseResult.getValue()))

Thanks and follow up issue :-(

@llvmbot
Copy link
Member

llvmbot commented Jun 2, 2023

@llvm/issue-subscribers-mlir

@tschuett
Copy link
Author

tschuett commented Jun 2, 2023

I believe this:


should mlir::Type().

@joker-eph
Copy link
Collaborator

Thanks! Fixed in a6a7a1b

@J-MR-T
Copy link
Contributor

J-MR-T commented Aug 20, 2023

if (::mlir::succeeded(parseResult.getValue()))

: error: no member named 'getValue' in 'mlir::OptionalParseResult'
      if (::mlir::succeeded(parseResult.getValue()))

Thanks and follow up issue :-(

I have the same issue, when trying to make my dialect extensible (let isExtensible = 1).

Manually going in the tblgen-generated .inc file and changing the line

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 (TestDialect doesn't seem to catch this issue) to prevent this from happening again might be good, but I fully understand that's a bit much to ask.

@joker-eph
Copy link
Collaborator

Also, I think a more thorough test of extensible dialects (TestDialect doesn't seem to catch this issue) to prevent this from happening again might be good,

The TestDialect is extensible, but unfortunately this particular combination also requires let useDefaultTypePrinterParser = 1; and the test dialect has let useDefaultTypePrinterParser = 0;...

@joker-eph joker-eph added this to the LLVM 17.0.X Release milestone Aug 20, 2023
@joker-eph
Copy link
Collaborator

joker-eph commented Aug 20, 2023

@J-MR-T if you can confirm that 87a1421 fixes your issue?

@joker-eph
Copy link
Collaborator

/cherry-pick 87a1421

@joker-eph joker-eph reopened this Aug 20, 2023
@llvmbot
Copy link
Member

llvmbot commented Aug 20, 2023

/branch llvm/llvm-project-release-prs/issue63072

@J-MR-T
Copy link
Contributor

J-MR-T commented Aug 21, 2023

@J-MR-T if you can confirm that 87a1421 fixes your issue?

I'm rebuilding now, thanks for looking at this so quickly! Will update you here asap.

@J-MR-T
Copy link
Contributor

J-MR-T commented Aug 21, 2023

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 let isExtensible = 1, so I believe this fixed it. Thank you again :).

joker-eph added a commit to joker-eph/llvm-project that referenced this issue Aug 23, 2023
tru pushed a commit that referenced this issue Aug 25, 2023
@github-project-automation github-project-automation bot moved this to Needs Triage in LLVM Release Status Sep 28, 2023
@tru tru moved this from Needs Triage to Needs Review in LLVM Release Status Sep 28, 2023
@tru tru moved this from Needs Review to Done in LLVM Release Status Sep 28, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 2, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 3, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 3, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 3, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 3, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 6, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 6, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 11, 2023
razmser pushed a commit to SuduIDE/llvm-project that referenced this issue Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

5 participants