diff options
| author | Sean Silva <silvasean@google.com> | 2020-12-11 14:20:03 -0800 |
|---|---|---|
| committer | Sean Silva <silvasean@google.com> | 2020-12-11 14:30:50 -0800 |
| commit | 444822d77a7fea28aa49edf24533c987efa1b2ee (patch) | |
| tree | 644332e90fbf1e87be2ce74a07d65618ca9707b1 /clang/unittests/Frontend/CompilerInvocationTest.cpp | |
| parent | 204bdc5322cc89603d503fb1f02a0eba19a1b496 (diff) | |
| download | llvm-444822d77a7fea28aa49edf24533c987efa1b2ee.zip llvm-444822d77a7fea28aa49edf24533c987efa1b2ee.tar.gz llvm-444822d77a7fea28aa49edf24533c987efa1b2ee.tar.bz2 | |
Revert "Revert "[mlir] Start splitting the `tensor` dialect out of `std`.""
This reverts commit 0d48d265db6633e4e575f81f9d3a52139b1dc5ca.
This reapplies the following commit, with a fix for CAPI/ir.c:
[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