diff options
| author | Sean Silva <silvasean@google.com> | 2020-12-09 17:50:03 -0800 |
|---|---|---|
| committer | Sean Silva <silvasean@google.com> | 2020-12-11 13:50:55 -0800 |
| commit | cab8dda90f48e15ee94b0d55ceac5b6a812e4743 (patch) | |
| tree | 49dcd99d454995ef9c5157b4f224a36418d0c9b2 /clang/unittests/Frontend/CompilerInvocationTest.cpp | |
| parent | 7b3470baf8bab1919e3ad4c18e2b776c1f7be2d5 (diff) | |
| download | llvm-cab8dda90f48e15ee94b0d55ceac5b6a812e4743.zip llvm-cab8dda90f48e15ee94b0d55ceac5b6a812e4743.tar.gz llvm-cab8dda90f48e15ee94b0d55ceac5b6a812e4743.tar.bz2 | |
[mlir] Start splitting the `tensor` dialect out of `std`.
This starts by moving `std.extract_element` to `tensor.extract` (this
mirrors the naming of `vector.extract`).
Curiously, `std.extract_element` supposedly works on vectors as well,
and this patch removes that functionality. I would tend to do that in
separate patch, but I couldn't find any downstream users relying on
this, and the fact that we have `vector.extract` made it seem safe
enough to lump in here.
This also sets up the `tensor` dialect as a dependency of the `std`
dialect, as some ops that currently live in `std` depend on
`tensor.extract` via their canonicalization patterns.
Part of RFC: https://llvm.discourse.group/t/rfc-split-the-tensor-dialect-from-std/2347/2
Differential Revision: https://reviews.llvm.org/D92991
Diffstat (limited to 'clang/unittests/Frontend/CompilerInvocationTest.cpp')
0 files changed, 0 insertions, 0 deletions