The object can't straddle the address space
wrap around, so I think it's OK to assume any
offsets added to the base object pointer can't
overflow. Similar logic already appears to be
applied in SelectionDAGBuilder when lowering
aggregate returns. Overflow flags scare me
so I'm not sure. I'm not sure the best
way to test for these, but some of these
avoid AMDGPU test regressions in a future
commit.
It would probably make sense to introduce
a getAddNUW helper for this instead
of littering the same boilerplate around
to create the flags.