Move operations to use MLIR Properties instead of Attributes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
This would be advantageous for many operations, and in many cases should be a simple conversion.
See:
https://mlir.llvm.org/OpenMeetings/2023-02-09-Properties.pdf
https://discourse.llvm.org/t/rfc-introducing-mlir-operation-properties/67846
And recent upstream MLIR commits migrating their dialects/IR over.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked MLIR Properties presentation and RFC, then inspect recent upstream MLIR commits that migrate dialects and operations. Identify the CIRCT operations still using Attributes and determine the migration scope; done means the relevant operations use MLIR Properties consistently and their existing behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100