[IR][Buider] (2/N) New IR builder for spmw - #30
Open
Fangtangtang wants to merge 17 commits into
Open
Conversation
Fangtangtang
marked this pull request as ready for review
March 20, 2026 14:34
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
follows cornell-zhang#570.
This PR introduces a new (experimental) MLIR IR builder.
Design Overview
The builder adopts a two-phase design:
ast_preprocessor)ir_builder)These two components are intended to serve as core infrastructure. They are expected to remain relatively stable over time and should not be modified frequently once the design matures.
In contrast, the
builtin/directory contains components related to syntax and semantic extensions. This part is designed to be highly extensible and is expected to evolve rapidly.Note that some of the existing implementations under
builtin/are not yet fully tested, they primarily serve as current feature support and examples for future semantic extensions.For more details, please refer to the README files in the corresponding directories.
Examples
New test cases are added under
tests/exp/:tests/exp/basic/: basic syntax and usage examples. These tests are lowered to the CPU backend for functionality validation.tests/exp/spmw/: tests and examples for the new SPMW programming interface. (Currently without backend codegen or execution validation.)Checklist
Please make sure to review and check all of these items: