[REFATOR][TIR] Phase out AllocConst#18761
Conversation
This PR phases out alloc const node in the TIR. This node was oroginally introduced to include embedded weights into the allocation. However, the presence of the particular IR couples the data allocation and the weight placement, which is not as desirable especialy when weights get large. A better approach is to have extra annotation on the allocation and store weights separately either outside module or as part of module/function attribute. As a result, we phases out this node which can help us to simplify code logic in the codebase.
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 systematically removes 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 large refactoring that phases out the AllocConst node from TIR. The changes are extensive, touching many parts of the codebase including core IR definitions, statement functors, IR builders, various transformation passes, codegen backends, and tests. The removal of AllocateConst and its related logic (AllocateConstNode, AllocateConstFrame, BindParams pass, ExtractPrimFuncConstants pass) seems to be thorough and consistent across all modified files. The code is cleaner and simplified as a result. The changes appear correct and align with the goal of decoupling data allocation and weight placement as described in the pull request description. I have no specific comments as the refactoring seems well-executed.
This PR phases out alloc const node in the TIR.
This node was oroginally introduced to include embedded weights into the allocation. However, the presence of the particular IR couples the data allocation and the weight placement, which is not as desirable especialy when weights get large. A better approach is to have extra annotation on the allocation and store weights separately either outside module or as part of module/function attribute.
As a result, we phases out this node which can help us to simplify code logic in the codebase.