diff options
author | Matthias Springer <me@m-sp.org> | 2024-11-29 11:12:27 +0900 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-29 11:12:27 +0900 |
commit | f2d500c61701fc50f5c0c2cd9660a93e15ecc9b9 (patch) | |
tree | 620f0dfbdab877d4dbb998583b259310668c13d1 /llvm/lib/Object/WasmObjectFile.cpp | |
parent | d106a39c3372b924668f203fedbce69aa986cf50 (diff) | |
download | llvm-f2d500c61701fc50f5c0c2cd9660a93e15ecc9b9.zip llvm-f2d500c61701fc50f5c0c2cd9660a93e15ecc9b9.tar.gz llvm-f2d500c61701fc50f5c0c2cd9660a93e15ecc9b9.tar.bz2 |
[mlir][Transforms] Dialect conversion: Fix bug in `UnresolvedMaterializationRewrite` rollback (#105949)
When an unresolved materialization (`unrealized_conversion_cast` op) is
rolled back, the mapping should be rolled back as well, regardless of
whether it is a source, target or argument materialization. Otherwise,
we accumulate pointers to erased IR in the `mapping`. This is harmless
in most cases, but can cause issues when a new operation is allocated at
the same memory location and the pointer is "reused".
It is not possible to write a test case for this because I cannot
trigger the pointer reuse programmatically.
Diffstat (limited to 'llvm/lib/Object/WasmObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions