This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/63405] [4.9/5 regression] ICE in cp_perform_integral_promotions, at cp/typeck.c:2084
- From: "gerrit.los at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 30 Sep 2014 20:44:03 +0000
- Subject: [Bug c++/63405] [4.9/5 regression] ICE in cp_perform_integral_promotions, at cp/typeck.c:2084
- Auto-submitted: auto-generated
- References: <bug-63405-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63405
--- Comment #7 from Gert-jan Los <gerrit.los at gmail dot com> ---
2014-09-30 20:39:22 CEST schrieb trippels at gcc dot gnu.org:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63405
>
> --- Comment #6 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
> Ah, the system compiler was build slightly before Jason's
> r215172 checkin from 20140911.
> gcc version 4.9.2 20140911 (prerelease) (GCC)
The code triggering the ICE has been part of my code base since at least
3 months. Within the project I used varying snaphots from trunk without
any problems.
I just retested with my system compiler [gcc version 4.9.1 (Debian 4.9.1-15)]
and now also get:
internal compiler error: in cp_perform_integral_promotions, at
cp/typeck.c:2066
To provide context I attached:
a) backtrace
b) bisect log
c) check script for creduce and bisect
d) my reduced testcase
At every git-bisect step I did a full bootstrap
$dir/$tgt/configure \
--prefix=$prefix \
--program-suffix=-snapshot \
--with-gmp=$prefix \
--with-mpfr=$prefix \
--with-mpc=$prefix \
--with-gnu-ld \
--enable-build-with-cxx --enable-cxx \
--enable-gold --enable-ld=default \
--enable-plugin --with-plugin-ld=ld.gold \
--enable-languages=c,c++ \
--enable-checking=release
make -j4 bootstrap
make install
As you can see in bisect.log some checkouts did not trigger the internal
compiler error.
I now see one possible defect in my testing methodology: I'm grepping
for the line number of the error message. Will retest with the fixed
check condition and report back tomorrow if the outcome changes.