[Bug other/31827] limits-exprparen.c: Pid 2297 received a SIGSEGV for stack growth failure

["dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>]

------- Comment #3 from dave at hiauly1 dot hia dot nrc dot ca  2007-05-24 00:53 -------
Subject: Re:  limits-exprparen.c: Pid 2297 received a SIGSEGV for stack growth
failure

> This test runs fine on my IA64 HP-UX and Linux boxes and on my HPPA HP-UX boxes
> where I have increased the stack size.  If I change the test case to do more
> nesting, I can get it to fail.

For the record, these are the limits on the machine where I saw
the failure:

-bash-2.05b$ ulimit -a
core file size        (blocks, -c) 2097151
data seg size         (kbytes, -d) 786432
file size             (blocks, -f) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 256
pipe size          (512 bytes, -p) 16
stack size            (kbytes, -s) 16384
cpu time             (seconds, -t) unlimited
max user processes            (-u) 76
virtual memory        (kbytes, -v) unlimited

I believe the stack size limit is double the default value.  The machine
has 7 GB of memory, so I doubt swap is an issue.

It's my personal belief that nesting routines to great depths
is bad design.  It makes debugging nearly impossible.  It's
possible we are hurt on hppa64 because the argument pointer isn't
a fixed register and this prevents the sibcall optimization
from occurring.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31827