Remove use of tuple for multiresult type storage
Move the results in line with the op instead. This results in each operation having its own types recorded vs single tuple type, but comes at benefit that every mutation doesn't incurs uniquing. Ran into cases where updating result type of operation led to very large memory usage. Differential Revision: https://reviews.llvm.org/D97652
parent
415c0cd6
Please register or sign in to comment