Skip to content

[torch-mlir] Bump LLVM to llvm/llvm-project@fc83eda4 #3282

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

Closed
wants to merge 12 commits into from

Conversation

aartbik
Copy link
Contributor

@aartbik aartbik commented May 3, 2024

(1) this brings in all "warnings" introduced in llvm/llvm-project#90413 (to be fixed by community)
(2) all errors due to new tosa int_div have been fixed
(3) all errors due to tensor output shape have been fixed

@aartbik aartbik requested a review from stellaraccident May 3, 2024 05:06
@aartbik
Copy link
Contributor Author

aartbik commented May 3, 2024

arghhh, it looks like that (at least some of) those warnings are turned into errors....
so we need to fix those first....

@aartbik
Copy link
Contributor Author

aartbik commented May 3, 2024

I fixed all the real errors, and fixed a lot of deprecated warning = error in most header files; fixing this in all cpp files seems a bit too daunting right now (and I cannot come up with an easy find/sed solution for this either). So I propose to have the warning != error for a bit, so this can go in, and fixing it can be done in a more manageable way.

@bjacob
Copy link
Contributor

bjacob commented May 7, 2024

I'm surprised that this PR isn't running into the same error as @jpienaar 's #3279 ,
https://github.com/llvm/torch-mlir/actions/runs/8930048121/job/24533271831?pr=3279#step:8:1358

  python: /_work/torch-mlir/torch-mlir/externals/llvm-project/mlir/lib/Dialect/Tensor/IR/TensorOps.cpp:1681: static void mlir::tensor::ExpandShapeOp::build(OpBuilder &, OperationState &, Type, Value, ArrayRef<ReassociationIndices>): Assertion `succeeded(outputShape) && "unable to infer output shape"' failed.

Maybe it's just because the current warnings-as-errors stop compilation before getting there?

In case you do run into this here, see the explanation: #3279 (comment)

@aartbik
Copy link
Contributor Author

aartbik commented May 7, 2024

I'm surprised that this PR isn't running into the same error as @jpienaar 's #3279 ,

Ah. very well possible that we never reach that point. I did fix some output checks with output shape (see e.g. flatten.mlir), so it definitely is at the same problematic update of MLIR.

Anyway, I am a bit stuck with this bump and could use some help (fixing the deprecations, or temporarily allowing me to remove the warning=error setting [which probably will run into jpienaar's issue first then])

@jpienaar
Copy link
Member

jpienaar commented May 7, 2024

I think it's great you fixed the deprecated warnings. We could land those even without a llvm rev bump and so make the rev bump simpler.

There is a lowering TOSA to Tensor side that is shown by one of the PyTorch tests, but could be a upstream change. I don't think torch-mlir bumps allow for cherry picks LLVM side, so it's probably up and through ;-)

@bjacob
Copy link
Contributor

bjacob commented May 7, 2024

Started a new integrate #3300, not yet wrapping the fixes from this PR but maybe we'll need to carry over some of the things you did here. For the deprecated declaration though, this is just disabling the warning.

@aartbik
Copy link
Contributor Author

aartbik commented May 8, 2024

Started a new integrate #3300, not yet wrapping the fixes from this PR but maybe we'll need to carry over some of the things you did here. For the deprecated declaration though, this is just disabling the warning.

Great, I will wait for that and see if we still want to salvage this PR (or start a new one)...

@aartbik
Copy link
Contributor Author

aartbik commented May 8, 2024

Looks like Benoit is already working on a much more recent sha, so closing this PR.
Thanks Benoit!

@aartbik aartbik closed this May 8, 2024
@aartbik aartbik deleted the bak branch May 8, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants