diff options
| author | Matthias Springer <springerm@google.com> | 2023-02-15 09:51:42 +0100 |
|---|---|---|
| committer | Matthias Springer <springerm@google.com> | 2023-02-15 10:04:54 +0100 |
| commit | 8f7e7400b74b362251dcf155e45f4097fd574196 (patch) | |
| tree | 238f497139561d5ecf07db5e43f737e98ed826e3 /lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.cpp | |
| parent | 462227f1150fc4a12f95a7a101de477c06d35ba7 (diff) | |
| download | llvm-8f7e7400b74b362251dcf155e45f4097fd574196.zip llvm-8f7e7400b74b362251dcf155e45f4097fd574196.tar.gz llvm-8f7e7400b74b362251dcf155e45f4097fd574196.tar.bz2 | |
[mlir][bufferization] Add restrict and writable attrs to to_tensor
`restrict` is similar to the C++ restrict keyword. Results of `to_tensor` that have the `restrict` attribute are guaranteed to not alias any other `to_tensor` result (after bufferization).
Note: Since `to_memref` ops are not supported by One-Shot Bufferize and all bufferizable ops follow DPS rules (i.e., the buffer of the result is the buffer of an operand or an alias thereof), the buffer of a `to_tensor` op that has the `restrict` attribute is always an entirely "new" buffer that is not aliasing with the future buffer of any tensor value in the entire program. This makes such `to_tensor` ops "safe" from a bufferization perspective; they cannot cause RaW conflicts.
Differential Revision: https://reviews.llvm.org/D144021
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.cpp')
0 files changed, 0 insertions, 0 deletions
