Current implementation of selecting best cost for epilog vectorization is sub-optimal and can be improved by ~2x. The problem is that isMoreProfitable is called twice. First we compare cost of each candidate against scalar cost and cache those ones that are more optimal than the scalar one. Second we travers via cached VFs and try to find most beneficial among them. The thing is that we don't really need to know which ones are better than the scalar one. It's simply enough to do the second step plus one compare against scalar cost.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This review may be stuck/dead, consider abandoning if no longer relevant.
Removing myself as reviewer in attempt to clean dashboard.
clang-format suggested style edits found: