[llvm-dev] Does middle-end pass need to consider some special type when doing optimization? Or letting back-end to revert the optimization accordingly? (original) (raw)
Florian Hahn via llvm-dev llvm-dev at lists.llvm.org
Tue Mar 23 03:16:17 PDT 2021
- Previous message: [llvm-dev] Does middle-end pass need to consider some special type when doing optimization? Or letting back-end to revert the optimization accordingly?
- Next message: [llvm-dev] Does middle-end pass need to consider some special type when doing optimization? Or letting back-end to revert the optimization accordingly?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 23, 2021, at 08:21, Luo, Yuanke <yuanke.luo at intel.com> wrote:
I prototyped the approach 1 at https://reviews.llvm.org/D99152 <https://reviews.llvm.org/D99152> and I realized that sometimes bitcast optimization in middle-end is helpful. For the test case of innerproduct(), we need extra effort eliminate llvm.x86.vector.amx.cast.x86amx.v256i32 by ourselves.
I think that’s expected, you might need to add some optimizations for the conversion intrinsic. But that can easily be limited to the AMX specific passes and all existing LLVM transformations should remain correct without changes.
Cheers, Florian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210323/e7f62ba9/attachment.html>
- Previous message: [llvm-dev] Does middle-end pass need to consider some special type when doing optimization? Or letting back-end to revert the optimization accordingly?
- Next message: [llvm-dev] Does middle-end pass need to consider some special type when doing optimization? Or letting back-end to revert the optimization accordingly?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]