On 01/11/15 04:40, Oleg Endo wrote:
Any particular reason why the SEQUENCE handling isn't done first, then the REG_INC and CALL insn handling? I'd probably explicitly return false if we had a sequence and none of its elements returned true. There's no need to check anything on the toplevel SEQUENCE to the best of my knowledge.No meaningful reason. Attached is an updated patch that applies on 4.8 and trunk. Bootstrapped on trunk i686-pc-linux-gnu. Tested with make -k check RUNTESTFLAGS="--target_board=sh-sim \{-m2/-ml,-m2/-mb,-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}" on trunk sh-elf. In the PR it has been reported, that the patch fixes the problems when building a native SH GCC. Although the related SH problem occurs only on 4.8, I'd like to install this on trunk and 4.9, too, to avoid future surprises. OK? Cheers, Oleg gcc/ChangeLog: PR target/64479 * rtlanal.c (set_reg_p): Handle SEQUENCE constructs.
OK. Jeff
