[REFACTOR][S-TIR] Migrate more transform to s_tir#18771
Conversation
Summary of ChangesHello @tqchen, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request undertakes a substantial refactoring effort within the TVM Tensor IR (TIR) framework. Its primary goal is to streamline the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request is a significant refactoring that migrates many TIR transformation passes from the tir namespace to the new s_tir namespace. The changes primarily consist of moving files, updating namespaces and include paths, and adjusting Python bindings and pipelines accordingly. The refactoring is well-executed, but I've found a few inconsistencies and typos that should be addressed to ensure correctness and maintain code quality. My main concerns are around pass configuration keys that were not updated during the migration, which could lead to tests not running with the intended configurations.
This PR migrate more transformations into s_tir, so tir namespace contains minimal determinisc passes that are essential for low levek codegen.
This PR migrate more transformations into s_tir, to reduce the passes in tir namespace.