Assuming this is used to split a memory access into smaller pieces,
the new access should still have the same aliasing properties as the
original memory access. As far as I can tell, this wasn't
intentionally dropped. It may be necessary to drop this if you are
moving the operand outside of the bounds of the original object in
such a way that it may alias another IR object, but I don't think any
of the existing users are doing this. Some of the uses widen into
unused alignment padding, which I think is OK.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
This is consistent with how we handle load splitting in other places; LGTM
llvm/lib/CodeGen/MachineFunction.cpp | ||
---|---|---|
483 | Only tangentially related, but I think this comment isn't true anymore. |
Only tangentially related, but I think this comment isn't true anymore.