Yes, there is a fair amount of history in the naming that is in need of cleaning up. The team at DFKI is also working on splitting the insertion of de-allocations and optimization of alloc placement into separate passes, so that one does not have to use the pipeline exactly as the hlo to lhlo lowering does.
I quite like the bufferize name (and have also started using it within kernel generator). So I would be all for standardizing on that.
@dfki-mako can you prioritize the cleanup, so that new uses can directly use better naming?
For patterns that implement the tensor to memref transformation, owning dialects can move them to a
bufferize.cc and maybe expose a
populateBufferizationPatterns so that the patterns can be mixed into a larger bufferization pass.