In microMIPS, labels need to know whether they are on code or data. This is
indicated with STO_MIPS_MICROMIPS and can be inferred by being followed
by instructions. For empty basic blocks, we can ensure this by emitting the
.insn directive after the label.
Also, this fixes some failures in our out-of-tree MIPS buildbots, for the
exception handling regression tests under: SingleSource/Regression/C++/EH
Nit: This comment isn't quite right since we emit .insn for empty BB's on all subtargets. I think you mean it only matters for microMIPS and MIPS16.