https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67573
--- Comment #5 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- (In reply to Oleg Endo from comment #4) > Maybe FPSCR_STAT_REG should be in the clobber list, too? Otherwise stores > of FP exception bits etc (get_fpscr builtin) could be wrongly CSE'd across > function calls... However, I don't know if this is a problem at the moment. I'm not sure whether it's a problem or not ATM too. The original issue happens with the aggressive allocation by LRA. If the scenario for FPSCR_MODES_REG is real, it could be seen with the old RA already.
