https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65979
--- Comment #8 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- (In reply to John Paul Adrian Glaubitz from comment #7) > Just built with gcc-4.9_4.9.2-7 which previously successfully built > gcc-4.9_4.9.2-10 [1] but fails to build gcc-4.9_4.9.2-16 [2]. It seems that latest 4.9 and 5.0 have some wrong code problem on this target. We should pin point it. My sh4 board has only 64MB RAM and it takes a week to get stage2 compiler for gcc-5. A reduced testcase for the cross compiler is deadly needed. It looks there are not so many target changes between http://http.debian.net/debian/pool/main/g/gcc-4.9/gcc-4.9_4.9.2-10.diff.gz and http://http.debian.net/debian/pool/main/g/gcc-4.9/gcc-4.9_4.9.2-16.diff.gz 2015-03-26 Oleg Endo <olege...@gcc.gnu.org> Backport from mainline 2015-03-26 Oleg Endo <olege...@gcc.gnu.org> * config/sh/t-sh (MULTILIB_EXCEPTIONS): Handle default endian. 2015-03-10 Oleg Endo <olege...@gcc.gnu.org> PR target/53988 * config/sh/sh.md (*tst<mode>_t_zero): Remove insns. 2015-03-03 Kaz Kojima <kkoj...@gcc.gnu.org> PR target/65249 * config/sh/sh.md (symGOT_load): Use R0 reg for operands[2] when called for __stack_chk_guard symbol. 2015-02-25 Kaz Kojima <kkoj...@gcc.gnu.org> Backport from mainline 2015-02-23 Kaz Kojima <kkoj...@gcc.gnu.org> PR target/65153 * config/sh/sh.md (movsicc_true+3): Remove peephole. * config/sh/sh-protos.h (replace_n_hard_rtx): Don't declare. * config/sh/sh.c (replace_n_hard_rtx): Remove. 2015-02-23 Oleg Endo <olege...@gcc.gnu.org> Backport from mainline 2015-02-23 Oleg Endo <olege...@gcc.gnu.org> PR target/65163 * config/sh/sh.md (swapbsi2, related peephole2): Use const_int -65536 instead of const_int 4294901760. 2015-01-08 Christian Bruel <christian.br...@st.com> PR target/64507 * config/sh/sh-mem.cc (sh_expand_cmpnstr): Check 0 length. of which revision number in FSF gcc svn are r221686, r221305, r221166, r220957, r220917, r219258 respectively. You can revert the above changes to see what happens. Looks safe changes to me, but some changes could reveal hidden problems. If the issue remains even if all those changes are reverted, there will be no easy way to narrow down.
