--- Comment #8 from kazu at gcc dot gnu dot org 2006-05-20 20:10 ---
*** This bug has been marked as a duplicate of 12454 ***
--
kazu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-03-23 11:27 ---
Subject: Re: Segmentation fault on testsuite case gcc.dg/20020425-1.c
> recursive gimplification will of course break at some point here. I remember
> Zdenek rewriting gimplification to a non
--- Comment #6 from rguenth at gcc dot gnu dot org 2006-03-17 14:32 ---
Forgot to mention - the ia64 build I was seeing this with was built with -g
-fno-inline and checking enabled.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21898
--- Comment #5 from rguenth at gcc dot gnu dot org 2006-03-17 14:29 ---
I see the same on ia64 for trunk.
Program received signal SIGSEGV, Segmentation fault.
0x402ed101 in gimplify_cond_expr (expr_p=0x2070aca8,
pre_p=0x607ffe8dc798, fallback=fb_none) at gimpli
--- Additional Comments From e9925248 at stud4 dot tuwien dot ac dot at
2005-06-03 20:46 ---
This is, what gdb shows, when it crashes:
Program received signal SIGSEGV, Segmentation fault.
0x08396436 in fold_convert_const_int_from_int (type=0xb7e80798, arg1=0xb7e78a20)
at ../.././gcc/fol
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-03
20:03 ---
you have all checking turned on, what do you expect. This is not a regression
and is just a stack
overflow. what is the first couple functions in the backtrace?
--
What|Removed
