This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/28277] __builtin_alloca with no limit in libstdc++
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jul 2006 22:48:40 -0000
- Subject: [Bug libstdc++/28277] __builtin_alloca with no limit in libstdc++
- References: <bug-28277-11211@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from pcarlini at suse dot de 2006-07-05 22:48 -------
(In reply to comment #5)
> The threads point is just a basic stack size issue: threads on linux have a
> fixed size which is often smaller than the main stack size limit.
Ok then.
> With an output width of 60 million, it's easy to see a failure, even on a main
> stack.
>
> hollerith:~/exp-string-width$ ulimit -Ss
> 8192
> hollerith:~/exp-string-width$ /home/mec/gcc-4.2-20060624/install/bin/g++ z1.cc
> hollerith:~/exp-string-width$ a.out > /dev/null
> Segmentation fault
Note, in general, I guess we are often going to fail anyway (at least for some
of the pointed out uses) only, throwing a bad_alloc exception instead of
seg-faulting, I hope that is acceptable...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28277