This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/70262] Segmentation fault with large stack array, no fault when alloca the same size
- From: "nickdu at msn dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 16 Mar 2016 23:09:31 +0000
- Subject: [Bug c/70262] Segmentation fault with large stack array, no fault when alloca the same size
- Auto-submitted: auto-generated
- References: <bug-70262-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70262
--- Comment #4 from nickdu at msn dot com ---
That doesn't explain why it works with alloca().
> From: gcc-bugzilla@gcc.gnu.org
> To: nickdu@msn.com
> Subject: [Bug c/70262] Segmentation fault with large stack array, no fault when alloca the same size
> Date: Wed, 16 Mar 2016 23:04:14 +0000
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70262
>
> --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> (In reply to nickdu from comment #2)
> > Why is this resolved as invalid? I realize I can increase my stack size.
> > However, I believe I'm currently under the limit. In addition, alloca of
> > the same size works.
>
>
> Well without a testcase that is self contained, there is no way to test it and
> make sure. Also is this on a secondary thread? Is so the thread stack space
> is usually much smaller unless you programatically increase it.
>
> --
> You are receiving this mail because:
> You reported the bug.
=