-
Notifications
You must be signed in to change notification settings - Fork 321
LLVM and StableHLO Update Schedule
hamptonm1 edited this page Oct 23, 2024
·
35 revisions
Update instructions can be found here.
| 2 Week period starting on (Monday) | Name | Github Username | Company | Status |
|---|---|---|---|---|
| 2024-02-05 | ||||
| 2024-02-19 | ||||
| 2024-03-04 | ||||
| 2024-03-18 | Philip Lassen | philass | Groq | done |
| 2024-04-01 | Megan Hampton | hamptonm1 | IBM | done |
| 2024-04-15 | Ferdinand Lemaire, Megan Hampton and Tong Chen | flemairen6 | AMD & IBM | done |
| 2024-04-29 | ||||
| 2024-05-13 | ||||
| 2024-05-27 | Yan Xu | Connor-XY | ByteDance | done |
| 2024-06-10 | Mike Essenmacher | mikeessen | IBM | done |
| 2024-06-24 | Boyana Norris | brnorris03 | Tsavorite | done |
| 2024-07-08 | Megan Hampton | hamptonm1 | IBM | done |
| 2024-07-22 | Chenhui Huang | YellowHCH | ByteDance | done |
| 2024-08-05 | Ferdinand Lemaire | flemairen6 | AMD | done |
| 2024-08-19 | Boyana Norris | brnorris03 | Tsavorite | |
| 2024-09-02 | Boyana Norris | brnorris03 | Tsavorite | done |
| 2024-09-16 | Megan Hampton | hamptonm1 | IBM | done |
| 2024-09-30 | Ferdinand Lemaire | flemairen6 | AMD | done |
| 2024-10-14 | Mike Essenmacher | mikeessen | IBM | done |
| 2024-10-28 | Megan Hampton | hamptonm1 | IBM | |
| 2024-11-11 | Ferdinand Lemaire | flemairen6 | AMD | |
| 2024-11-25 | Sunny Anand | Sunny-Anand | IBM | |
| 2024-12-09 | ||||
| 2024-12-23 |
Rotation based on history:
- [Nvidia, Microsoft, AMD, IBM, Groq, ByteDance, Microsoft, AMD, IBM, Groq] then repeat
Past schedules:
2023 updates
| 2 Week period starting on (Monday) | Name | Github Username | Company | Status |
|---|---|---|---|---|
| 2023-01-23 | Christopher Bate | christopherbate | Nvidia | done |
| 2023-02-06 | Stella Stamenova | sstamenova | Microsoft | done |
| 2023-02-20 | Mike Essenmacher | mikeessen | IBM | done |
| 2023-03-06 | Ashay Rane | ashay | Microsoft | done |
| 2023-03-20 | Dominik Montada | gargaroff | AMD | done |
| 2023-04-03 | Philip Lassen | philass | Groq | done |
| 2023-04-17 | Megan Hampton | hamptonm1 | IBM | done |
| 2023-05-01 | Dominik Montada | gargaroff | AMD | done |
| 2023-05-15 | Chen Chongsong | chenchongsong | ByteDance | done |
| 2023-05-29 | Philip Lassen | philass | Groq | done |
| 2023-06-12 | Christopher Bate | christopherbate | Nvidia | done |
| 2023-06-26 | Ashay Rane | ashay | Microsoft | done |
| 2023-07-10 | Ferdinand Lemaire | flemairen6 | AMD | done |
| 2023-07-24 | Mike Essenmacher | mikeessen | IBM | done |
| 2023-08-07 | Groq | |||
| 2023-08-21 | Yan Xu | Connor-XY | ByteDance | done |
| 2023-09-04 | Jacky Chen | jcwchen | Microsoft | |
| 2023-09-18 | Ferdinand Lemaire & Maximilian Bartel | flemairen6 & maxbartel | AMD | done |
| 2023-10-02 | IBM | |||
| 2023-10-16 | Philip Lassen | philass | Groq | |
| 2023-10-30 | Christopher Bate | christopherbate | Nvidia | |
| 2023-11-13 | Mike Essenmacher | mikeessen | IBM | |
| 2023-11-27 | Ferdinand Lemaire | flemairen6 | AMD | done |
| 2023-12-11 | Megan Hampton | hamptonm1 | IBM | done |
| 2023-12-25 |
- The first build on Windows/Jenkins of an LLVM update can sometimes time out or run out of space. This is because LLVM needs to be rebuilt instead of using the caches. If you are doing an update and the first build fails because of these reasons, feel free to restart the build - this should use the cache and succeeed. If it continues to fail, you should investigate.
- Our Jenkins CIs also cache LLVM compiled versions. When you are working with new ones, the servers may run out of space. If you suspect this, feel free to contact @gongsu832 or @AlexandreEichenberger and we will clean up space on these servers.
- It can be helpful to first look over the list of changes in upstream MLIR before starting the upgrade. You can do that with the following command from inside the
llvm-projectdirectory. It will give you the list of commits that will be added starting from oldest to newest and include only commits that modified MLIR files (as opposed to other projects in LLVM):
git log ^[current commit hash] [target commit hash] --reverse -- mlir/ > upgrade.log- Sometimes you want to look for changes of a specific string when a function definition changes for example. Using the GitHub search is often not successful. You can search for commits that changed that string with:
git log -G <regex>. A good trick is than to copy the commit id and search for that on GitHub. This search will normally find the commit/PR and has nice highlighting of all the changes.