[llvm-dev] Splitting 'expand' into 'split' and `expand`.

[Matt Arsenault via llvm-dev]

> On Aug 12, 2015, at 10:25 AM, Dylan McKay via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Expand should always expand the node into a different pattern (such as MULHU expanding to MUL and a copy of the top half).
> Split will always split an operation into several smaller, operations (such as 128-bit addition being split into a 64-bit addition and a 64-bit addition with carry)

Are you primarily trying to avoid Expand being implemented as a lib call with a larger type? Are there other cases where you want to avoid a different type of expansion besides a call? Before I’ve wanted to have ExpandLibcall be a separate action from Expand, which is somewhat similar idea.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150812/e123e133/attachment-0001.html>