OMP_STACKSIZE silently exceeded

[Janne Blomqvist]

On Tue, Oct 8, 2019 at 8:38 AM Eatdirt <eatdirt@protonmail.com> wrote:
>
> On 07/10/2019 20:52, Tobias Burnus wrote:
> > Hi Chris,
> >
> > On 10/7/19 4:13 PM, Eatdirt wrote:
> >> I just want to report something which is standard-compliant, but utterly
> >> sad about the behaviour of OMP_STACKSIZE.
> >
> > I asked Jakub, GCC's OpenMP expert – and he replied (thanks!):
> >
> > "That is standard behavior of pthread_attr_setstacksize etc.,
> > I think the default is that there is one page guardsize, easy to verify
> > with
> > strace, but if they access beyond that, of course something else can be
> > mapped there.  We can't default to gigabytes of guard areas, that is very
> > costly and impossible on 32-bit targets."
> >
> > Cf.
> > http://man7.org/linux/man-pages/man3/pthread_attr_setstacksize.3.html
> > and http://man7.org/linux/man-pages/man3/pthread_attr_setguardsize.3.html
> >
> > Cheers,
>
>
> Good to know! Thanks for the links!!!

Does -fstack-check and/or -fstack-clash-protection help?

(I was under the impression that something like
-fstack-clash-protection was the default nowadays, but apparently I
was wrong)


-- 
Janne Blomqvist