<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 9, 2012, at 4:20 AM, Chandler Carruth wrote:</div><blockquote type="cite"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+ SDValue NewShiftAmt = DAG.getConstant(ShiftAmt + AMShiftAmt, MVT::i8);<br>
<br>
Please use getShiftAmountTy.<br></blockquote><div><br></div><div>None of the other address mode computations use it. =/ It seems like goodness, but it requires threading a TargetLowing handle into this code. I've got 4 or 5 more patches queued up behind this that changing the interface in that way would make kind of annoying. I'd prefer to clean up all of the i8 shift types in one pass afterward. That sound good to you?</div></div></blockquote><br></div><div>This isn't necessary. This file is X86-specific (and isn't trying to handle vector shifts), so the shift type is fixed to MVT::i8. getShiftAmountTy() is only needed in target-independent parts of codegen where you don't know what the shift type will be.</div><div><br></div><div>--Owen</div><br></body></html>