Re: [gomp4 11/14] libgomp: avoid variable-length stack allocation in team.c

2015-10-21 Thread Jakub Jelinek
On Tue, Oct 20, 2015 at 09:34:33PM +0300, Alexander Monakov wrote: > NVPTX does not support alloca or variable-length stack allocations, thus > heap allocation needs to be used instead. I've opted to make this a generic > change instead of guarding it with an #ifdef: libgomp usually leaves thread

Re: [gomp4 11/14] libgomp: avoid variable-length stack allocation in team.c

2015-10-20 Thread Bernd Schmidt
On 10/20/2015 11:36 PM, Alexander Monakov wrote: Thanks, NVPTX will need a low buf_fixed size, perhaps 64 bytes or so. What about the generic case, should it use a more generous threshold, or revert to existing unbounded alloca? Any ideas how big is the required allocation size is in practice?

Re: [gomp4 11/14] libgomp: avoid variable-length stack allocation in team.c

2015-10-20 Thread Alexander Monakov
On Tue, 20 Oct 2015, Bernd Schmidt wrote: > On 10/20/2015 08:34 PM, Alexander Monakov wrote: > > NVPTX does not support alloca or variable-length stack allocations, thus > > heap allocation needs to be used instead. I've opted to make this a generic > > change instead of guarding it with an #if

Re: [gomp4 11/14] libgomp: avoid variable-length stack allocation in team.c

2015-10-20 Thread Bernd Schmidt
On 10/20/2015 08:34 PM, Alexander Monakov wrote: NVPTX does not support alloca or variable-length stack allocations, thus heap allocation needs to be used instead. I've opted to make this a generic change instead of guarding it with an #ifdef: libgomp usually leaves thread stack size up to libc,