From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12479 invoked by alias); 29 Jan 2013 21:17:50 -0000 Received: (qmail 12355 invoked by uid 48); 29 Jan 2013 21:17:07 -0000 From: "tg at mirbsd dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52306] ICE in cselib_record_set, at cselib.c:2158 Date: Tue, 29 Jan 2013 21:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tg at mirbsd dot org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Summary Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg02683.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D52306 Thorsten Glaser changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ICE in CSE |ICE in cselib_record_set, | |at cselib.c:2158 --- Comment #12 from Thorsten Glaser 2013-01-29 21:1= 7:04 UTC --- # cat /usr/bin/g++ #!/bin/mksh-static /usr/bin/g++-4.6 "$@" && exit 0 /usr/bin/g++-4.6 "$@" -O1 && exit 0 exec /usr/bin/g++-4.6 "$@" -O0 Has anyone thought of making GCC do that automatically? It already retries = on ICEs to weed out possibly bad memory=E2=80=A6 if we have an ICE like this s= pecific case, where we *know* optimisation makes a difference and it=E2=80=99s a bu= g in the compiler, we could just retry lowering the optimisation level each time. (My shell script is very suboptimal as it always retries twice. I=E2=80=99m= using it only for the second time now, and both times only during the build, after a= ll configury has been run. Some C++ code seems to exercise PR52306 more than, = say, libvirt which has only one occurrence (times two)=E2=80=A6)