[PATCH] D21534: GlobalISel: first outline of legalization interface.

Tim Northover via llvm-commits llvm-commits at lists.llvm.org
Wed Jun 22 13:58:34 PDT 2016


On 22 June 2016 at 13:16, Quentin Colombet <qcolombet at apple.com> wrote:
> Let me explain a bit why I think it is sufficient.
> <4 x float> and <4 x i32> are <4 x 32-bit> for most operations (load, store,
> and, shuffle, etc.). The only cases where that make a difference AFAICT are
> arithmetic operations. However, for those, the type is actually encoded in
> the opcode, e.g., fadd vs. add (we do not have G_FADD yet but I think we
> should :)). In other word, when type matters, the opcode should give us the
> information otherwise we should be able to get away of that business.

Ah, I see. That would certainly be simpler in this segment of code.
Have you thought about how addresss-spaces would fit in here (cf
Matt's comment about different requirements)? It seems like they might
have to be part of the lower-level type system.

Tim.


More information about the llvm-commits mailing list