This quickly triggers a fuzzbug when two classes have the same spillslot size. It turns out that this is caused by the parallel move resolver not supporting cross-class moves, which can happen if the parallel involves a spillslot used by different classes before/after the move.
This quickly triggers a fuzzbug when two classes have the same spillslot size. It turns out that this is caused by the parallel move resolver not supporting cross-class moves, which can happen if the parallel involves a spillslot used by different classes before/after the move.