-
Notifications
You must be signed in to change notification settings - Fork 348
Bump LLVM commit to 20ed5b1f4587 #2799
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
Bump LLVM commit to 20ed5b1f4587 #2799
Conversation
stablehlo to 49dc86c0df9ac3a8a556208674204b0f68d8eb6d Signed-off-by: Ferdinand Lemaire <[email protected]>
Can one of the admins verify this patch? |
Would someone know why the MacOS build is failing? The error seems to come from stablehlo and to be self-contained in a file from there so I would assume it's not the bump that made it fail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
The related error message:
is long vs. long long a special case on Mac? |
|
Right, but since it seems to be a stablehlo contained problem (the problematic function is defined and only used in |
Unless they already knew about the problem, I think opening an issue at stablehlo is probably the way to go. |
Just checked and it appears they fixed it already. It seems they bump LLVM to a newer commit, so I'll bump again to a new LLVM to match, and bump stablehlo to the fixed commit. |
Thanks @flemairen6 for your hard work! Are you looking at LLVM commit |
Yes for the LLVM commit, but I was planning to use |
Revert the changes to properties from stablehlo and fix some references where variable names had changed. Signed-off-by: Ferdinand Lemaire <[email protected]>
Can one of the admins verify this patch? |
@chentong319 I see |
Agreed! Makes sense to me :) |
@flemairen6 You can remove or comment out the |
unstable Signed-off-by: Ferdinand Lemaire <[email protected]>
Can one of the admins verify this patch? |
@jenkins-droid test this please |
@flemairen6 New issue... it seems like the following backend tests are failing:
|
@chentong319 I created an issue to track the lit test fix: #2803 |
I could reproduce the failing tests, but I have a hard time finding out the root cause, I'm seeing a double free in the OMRunner. My knowledge on the backend is really limited, who would be a Backend expert that could help me with this? |
When a lit test failed only on Mac, it is usually caused by the different order of DAG operations. The solution is either to avoid ambiguity in code gen or modify the CHECK in lit test. |
@flemairen6 Do you have the exact error message that you can post here? I see |
Looks like it's segfaulting so I don't think it's just a CHECK issue - the same bug seems to trigger on other architectures too |
I don't have a lot to work with, this is the full trace. Looks like some JSON didn't get dumped, or did with a wrong format, it's hard to tell |
I looked into the backend test failures. They are related to ONNXUniqueOp. The new buffer deallocation in llvm cannot handle unrealized_conversion_cast correctly. Now deallocation is generated for allocated memref used in ReturnOp. When I modify the code to avoid the unrealized_conversion_cast, the test case is fine. Comment: I create #2820 to fix this issue. No need to worry about it if the PR is fine. |
The PR will fail on some cast related test if the deallocation pass is commented. I use test_cast_DOUBLE_to_FLOAT16_cpu as an example. The failure is after onnx-mlir generated llvm IR. In this test case, the only special op is arith.truncf. I do noticed that the definition of TruncFOp is changed. But the output of @hamptonm1 Do you have some bandwidth to track this problem down? To me, the first thing is to verify the lowering arith.trucf to llvm.fptrunc is correct in the new version of llvm. Then focus on the lowering of llvm.fptrunc. |
Okay I have a few things I need to take care of and then I can try to look at this myself. Thanks! |
@flemairen6 Can you do me a favor and update your description for this PR? It seems like you checked out |
@jenkins-droid test this please |
@chentong319 I merged your recent update into the PR and now it seems like all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Jenkins Linux ppc64le Build #13916 [push] Bump LLVM commit to 20ed... started at 13:09 |
Jenkins Linux amd64 Build #14886 [push] Bump LLVM commit to 20ed... started at 11:59 |
Jenkins Linux s390x Build #14891 [push] Bump LLVM commit to 20ed... started at 12:59 |
Jenkins Linux amd64 Build #14886 [push] Bump LLVM commit to 20ed... passed after 2 hr 13 min |
Jenkins Linux s390x Build #14891 [push] Bump LLVM commit to 20ed... passed after 2 hr 14 min |
Jenkins Linux ppc64le Build #13916 [push] Bump LLVM commit to 20ed... passed after 3 hr 7 min |
Bump LLVM commit to 20ed5b1f4587 and Stablehlo to fd0c20a10