When generating MIR for JSOp::TableSwitch, IonBuilder had an optimization that replaced the switch input with the case value at the start of each case block. This let optimizations know the value of the switch input inside the block.

WarpBuilder doesn't have an equivalent optimization, and range analysis doesn't know anything about tableswitch. It's probably easiest to fix this in build_JumpTarget instead of messing around with range analysis.