Update computeMinimumValueSizes to check if an instruction's operands
can safely be truncated.
If more than MinBW bits are demanded by for the operand or if the
operand is a constant and cannot be safely truncated, it is not safe to
evaluate the instruction in the narrower MinBW. Skip those cases.
We're effectively working around this.
Does make me wonder: If we make the Worklist work on Uses rather than Values, could we handle this directly in this loop?