-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimize difference between Intel port and OpenAI Triton #2030
Comments
@etiotto I moved |
After PR #2064 lands we will have 48 files with differences (down from 66):
|
Part of #2030 Part of #2824 For all other compilers the situation is about the same, it is expected that they are already in the paths. I don't think it should be any different for Windows. --------- Signed-off-by: Anatoly Myachev <[email protected]>
Part of #2030 Part of #2824 For all other compilers the situation is about the same, it is expected that they are already in the paths. I don't think it should be any different for Windows. --------- Signed-off-by: Anatoly Myachev <[email protected]>
…modifying lit config file (#2965) Part of #2030 Signed-off-by: Anatoly Myachev <[email protected]>
Status update:
|
Status update:
|
@anmyachev As there are some new changes for Windows, can you please revisit to double check if any of the Windows changes can be upstreamed? |
Phil was pretty unequivocal here: triton-lang/triton#5372 |
I am aware that Phil doesn't want Windows support in general, but we were able to still upstream some of the changes, so wonder if there are any Windows related changes that we could upstream. For example:
|
These changes are upstreamed: triton-lang/triton@4523d38, but I don't see what else can be upstreamed right now. |
Thanks for upstreaming and confirming. |
I took a first pass at the difference between the latest OpenAI Triton code upstream and our fork. We have 66 common files showing a difference. To obtain the difference use the following command on the latest
llvm-target
(the commit ID is from our last merge):The file containing a difference are in the following table. The 2nd column labeled "Upstreamable" indicates whether the diff. in that file are upstreamable or not, and whether we should attempt to upstream them now or in the future (i.e. we need to upstream our BE in third_party in order to upstream the difference). Specificaly:
The 3rd column indicates whether we should move the difference (or the file) in the third_party/intel directory. The 4th column indicates whether the difference could be reduced or not.
The following table summarizes features (or lack thereof) that need to be redesigned in order to remove the difference thy cause in common files. For example "warp layout" is a feature of our advanced codegen path which requires some redesign to avoid changes in common files.
The text was updated successfully, but these errors were encountered: