diff options
| author | Tomás Longeri <tlongeri@google.com> | 2023-10-18 16:53:18 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-18 16:53:18 +0200 |
| commit | 5a600c23f9e01f58bac09a8fad096e194fc90ae2 (patch) | |
| tree | 3fea326184dc36ea2935c635351752459a403146 /llvm/docs/tutorial | |
| parent | a3a0f59a1e1cb0ac02f06b19f730ea05a6541c96 (diff) | |
| download | llvm-5a600c23f9e01f58bac09a8fad096e194fc90ae2.zip llvm-5a600c23f9e01f58bac09a8fad096e194fc90ae2.tar.gz llvm-5a600c23f9e01f58bac09a8fad096e194fc90ae2.tar.bz2 | |
[mlir][python] Expose `PyInsertionPoint`'s reference operation (#69082)
The reason I want this is that I am writing my own Python bindings and
would like to use the insertion point from
`PyThreadContextEntry::getDefaultInsertionPoint()` to call C++ functions
that take an `OpBuilder` (I don't need to expose it in Python but it
also seems appropriate). AFAICT, there is currently no way to translate
a `PyInsertionPoint` into an `OpBuilder` because the operation is
inaccessible.
Diffstat (limited to 'llvm/docs/tutorial')
0 files changed, 0 insertions, 0 deletions