http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52306
Thorsten Glaser <tg at mirbsd dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE in CSE |ICE in cselib_record_set,
| |at cselib.c:2158
--- Comment #12 from Thorsten Glaser <tg at mirbsd dot org> 2013-01-29 21:17: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… if we have an ICE like this specific
case, where we *know* optimisation makes a difference and it’s a bug 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’m using it
only for the second time now, and both times only during the build, after all
configury has been run. Some C++ code seems to exercise PR52306 more than, say,
libvirt which has only one occurrence (times two)…)
