If the loaded memory size was smaller than the result size, this would
produce out of bounds memory accesses. I'm wondering if we need a
distinct narrow memory legalize action type, since a case I care about
is decomposing a 4-byte unaligned access into 4 extending loads, which
would leave the original result register type. I'm currently awkwardly
using narrowScalar to handle unaligned accesses that need to be split.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
This seems reasonable to me.
llvm/lib/CodeGen/GlobalISel/LegalizerHelper.cpp | ||
---|---|---|
3125–3126 | Can we have some debug output explaining what's happening here? |
Can we have some debug output explaining what's happening here?