https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92488
--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Segher Boessenkool from comment #5) > operands[2] needs an earlyclobber as well (it is written while some > operands are still read later). Everything else is fine as far as I > can see :-) I originally had that early clobber as well, but the only operand still read later is operands[3] which is already early clobber, so do we really need that? If we mark operands[2] early clobber, then we'll never be able to assign operands[1] and operands[2] to the same hw register, which they could be. If you still want operands[2] marked early clobber, I can do that.
