This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/38059] [4.4/4.5/4.6 Regression] Compile time regression for gcc.dg/20020425-1.c
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 5 Mar 2011 14:13:57 +0000
- Subject: [Bug middle-end/38059] [4.4/4.5/4.6 Regression] Compile time regression for gcc.dg/20020425-1.c
- Auto-submitted: auto-generated
- References: <bug-38059-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38059
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.03.05 14:13:46
Ever Confirmed|0 |1
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-05 14:13:46 UTC ---
Hm, if we have that deep recursion then aren't we prone to the original
problem the test tests for, a stack overflow in the C parser?
And it does ...
$ /obj/trunk-g/gcc/xgcc -B/obj/trunk-g/gcc/
/home/richard/src/trunk/gcc/testsuite/gcc.dg/20020425-1.c -ansi
-pedantic-errors -S -o 20020425-1.s
xgcc: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
if one doesn't raise stack limits like dejagnu does.
I think this is definitely worth fixing (removing the recursion in
gimplify_cond_expr). A regression to pre-tree-SSA.