[llvm-dev] [GlobalISel] Legalization for memcpy family intrinsics

[Amara Emerson via llvm-dev]

> On Dec 16, 2020, at 6:47 AM, Devadasan, Christudasan <Christudasan.Devadasan at amd.com> wrote:
> 
> Hi All,
>  
> I was trying to legalize the family of memcpy intrinsics (memcpy, memmove and memset) for AMDGPU and found that the combiner functions optimizeMemcpy, optimizeMemmove and optimizeMemset implemented in CombinerHelper.cpp pretty much handle these lowering.
>  
> Can we move these functions to Legalizer entirely and perform a custom legalization to handle their expansion?
> The reason is, in the Combiner it is more of an optimization action rather than something required always for correctness.
Right, that’s how this is implemented in SelectionDAG too, it’s an optimization that may or may not fire depending on the heuristics.
>  
> On the other hand, if these combiner expansions turned out to be unavoidable, we should move these function into a common file.
> In that way, both Legalizer and Combiner can take advantage of them.
I think refactoring it to be shared is ok, but I and others disagree that this is a legalization issue rather than a combiner. There is no question of legality here, the target should be able to handle these opcodes. If they’re not legal for your target, then you could simply not use the expansion combines and handle them using custom legalization like any other operation.

Amara
>  
> Regards,
> CD

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201216/572508ac/attachment.html>