aboutsummaryrefslogtreecommitdiff
path: root/flang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorAlex Zinenko <zinenko@google.com>2021-03-10 11:46:36 +0100
committerAlex Zinenko <zinenko@google.com>2021-03-10 13:07:26 +0100
commita776942ba1aa0e381dd41a01de4b54fc5dc431cd (patch)
tree1aa06a5544ca5a8f29b178270202b949e2e34673 /flang/lib/Frontend/CompilerInvocation.cpp
parent0af53de3699997d04bc0e23f6b366c26a4a9268b (diff)
downloadllvm-a776942ba1aa0e381dd41a01de4b54fc5dc431cd.zip
llvm-a776942ba1aa0e381dd41a01de4b54fc5dc431cd.tar.gz
llvm-a776942ba1aa0e381dd41a01de4b54fc5dc431cd.tar.bz2
[mlir] squash LLVM_AVX512 dialect into AVX512
The dialect separation was introduced to demarkate ops operating in different type systems. This is no longer the case after the LLVM dialect has migrated to using built-in vector types, so the original reason for separation is no longer valid. Squash the two dialects into one. The code size decrease isn't quite large: the ops originally in LLVM_AVX512 are preserved because they match LLVM IR intrinsics specialized for vector element bitwidth. However, it is still conceptually beneficial to have only one dialect. I originally considered to use Tablegen multiclasses to define both the type-polymorphic op and its two intrinsic-related instantiations, but decided against it given both the complexity of the required Tablegen input and its dissimilarity with the rest of ODS-defined ops, both potentially resulting in very poor maintainability. Depends On D98327 Reviewed By: nicolasvasilache, springerm Differential Revision: https://reviews.llvm.org/D98328
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions