If the LocalStackSlotAlloction pass has already fixed the offset
for the object during operand folding, check if the offset is an
inline immediate.
There are a couple remaining issues separate from this patch
that need to be corrected before this can be committed.
LocalStackSlotAlloctation decides if it didn't need to put any
frame base registers in that it shouldn't create the pre-allocated
area, so no offsets are known.
Additionally there are code regressions when the base frame index
is folded into an instruction at the expensive of the offset.
e.g. an add fi, offset folds the frame index instead of the single
use offset, instead of materializing the frame index which is re-used
in multiple instructions.