This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/81290] [8 Regression] ICE in update_br_prob_note
- From: "hubicka at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 04 Jul 2017 11:37:22 +0000
- Subject: [Bug rtl-optimization/81290] [8 Regression] ICE in update_br_prob_note
- Auto-submitted: auto-generated
- References: <bug-81290-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81290
--- Comment #7 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Hmm, I configured with:
../configure --host=x86_64-pc-linux-gnu --target=powerpc-e500v2-linux-gnuspe
--build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/powerpc-e500v2-linux-gnuspe/gcc-bin/8.0.0-alpha20170702
--includedir=/usr/lib/gcc/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702/include
--datadir=/usr/share/gcc-data/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702
--mandir=/usr/share/gcc-data/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702/man
--infodir=/usr/share/gcc-data/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702/info
--with-gxx-include-dir=/usr/lib/gcc/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702/include/g++-v8
--with-python-dir=/share/gcc-data/powerpc-e500v2-linux-gnuspe/8.0.0-alpha20170702/python
--enable-languages=c,c++ --enable-obsolete --enable-secureplt --disable-werror
--with-system-zlib --disable-nls --enable-checking=yes --disable-esp
--enable-libstdcxx-time --enable-poison-system-directories
--with-sysroot=/usr/powerpc-e500v2-linux-gnuspe --disable-bootstrap
--enable-__cxa_atexit --enable-clocale=gnu --disable-multilib --disable-altivec
--disable-fixed-point --enable-e500-double --enable-targets=all
--disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp
--disable-libcilkrts --disable-libmpx --disable-vtable-verify --disable-libvtv
--disable-libquadmath --enable-lto --with-isl --disable-isl-version-check
--enable-libsanitizer
and it compiles just fine for me. The ICE at that specific backtrace was fixed
in quite robust way. Are you sure you did not test unpatched tree?