This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: C++14 implementation status
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: libstdc++ at gcc dot gnu dot org
- Cc: Ed Smith-Rowland <3dw4rd at verizon dot net>, Ulrich Drepper <drepper at gmail dot com>, Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Date: Thu, 13 Jun 2013 10:37:17 -0500
- Subject: Re: C++14 implementation status
- References: <CAH6eHdQb=PhvSVhE79Gv_0CxNq1PNDAtnHqRN+qAHn3-rhtWzA at mail dot gmail dot com> <51B5EFD6 dot 4060806 at verizon dot net> <alpine dot DEB dot 2 dot 10 dot 1306101735450 dot 28948 at stedding dot saclay dot inria dot fr> <CAOPLpQd2ecHpGQP78buFVk9MSzCrwj9+DQKNOQagFYNfDpu5_Q at mail dot gmail dot com> <51B9DE42 dot 3050409 at verizon dot net> <alpine dot DEB dot 2 dot 10 dot 1306131704190 dot 14262 at laptop-mg dot saclay dot inria dot fr>
On Thu, Jun 13, 2013 at 10:15 AM, Marc Glisse
>> allocation if the size request is too large for a stack frame.
>> Finding a meaningful upper limit of stack frame size might be a trick.
>
>
> I think 2048 bytes is a good start as a switch point between stack and heap
> ;-)
Well, that is lot :-)
Also, this is usually a per-user runtime environment
variable... I suspect we need to gather lot of information
about what the C-land does in these cases for VLAs.
-- Gaby