[REFACTOR][S-TIR] Migrate meta_schedule into s_tir namespace#18735
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 performs a significant refactoring by moving 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 undertakes a significant refactoring to migrate the meta_schedule module into the s_tir namespace. The changes are extensive, involving file moves, namespace updates in C++ and Python code, and adjustments to build configurations. Overall, the migration appears to be thorough. I've identified a critical issue where an FFI function registration was accidentally removed, which would break Python bindings. I also have a concern about the scope of changes in CMakeLists.txt. Please see my detailed comments.
| return TuningRecord(trace, workload, run_secs, target, args_info); | ||
| }) | ||
| .def_method("meta_schedule.TuningRecordAsMeasureCandidate", | ||
| .def_method("s_tir.meta_schedule.TuningRecordAsMeasureCandidate", |
There was a problem hiding this comment.
The FFI registration for TuningRecordAsMeasureCandidate seems to have been accidentally removed instead of being renamed. This will break the TuningRecord.as_measure_candidate() method in Python. Please add it back.
| .def_method("s_tir.meta_schedule.TuningRecordAsMeasureCandidate", | |
| .def_method("s_tir.meta_schedule.TuningRecordAsMeasureCandidate", &TuningRecordNode::AsMeasureCandidate) | |
| .def_method("s_tir.meta_schedule.TuningRecordAsJSON", &TuningRecordNode::AsJSON) |
|
|
||
| # Source file lists | ||
| tvm_file_glob(GLOB_RECURSE COMPILER_SRCS | ||
| src/auto_scheduler/*.cc |
There was a problem hiding this comment.
This PR migrates meta_schedule into the s_tir namespace.
guan404ming
left a comment
There was a problem hiding this comment.
Thanks for the great work! LGTM
This PR migrates meta_schedule into the s_tir namespace.