Fix invalid cc_status after [const_][us]mulsi3_highpart
Andreas Schwab
schwab@linux-m68k.org
Thu Aug 2 17:25:00 GMT 2018
On Jul 17 2018, Andreas Schwab <schwab@linux-m68k.org> wrote:
> The mulu.l insn sets the CC according to the 64-bit result, but we are
> only using the high part, so the Z flag cannot be used. The other flags
> would still be valid, but we have no cc_status flag for that case.
>
> * config/m68k/m68k.md (umulsi3_highpart+1, const_umulsi3_highpart)
> (smulsi3_highpart+1, const_smulsi3_highpart): Add CC_STATUS_INIT.
>
> testsuite/:
> * gcc.target/m68k/mulsi_highpart.c: New test.
Backported to gcc-8 branch to fix PR target/86820.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
More information about the Gcc-patches
mailing list