[Bug middle-end/13182] -fstack-check probes too distant when allocating on stack

2017-05-30 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182 --- Comment #10 from Eric Botcazou --- > To be clear: x86/Linux and x86-64/Linux (and for them there is no protection > area during the probing). I misremembered: there is exactly one page of protection area for them because of the way the unwin

[Bug middle-end/13182] -fstack-check probes too distant when allocating on stack

2017-05-30 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182 --- Comment #9 from Eric Botcazou --- > Right, the Ada runtime uses an alternate signal stack for specific platforms. To be clear: x86/Linux and x86-64/Linux (and for them there is no protection area during the probing).

[Bug middle-end/13182] -fstack-check probes too distant when allocating on stack

2017-05-30 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182 --- Comment #8 from Eric Botcazou --- > I'm not sure if the the probing offset is large enough for this purpose > because the kernel keeps pushing more and more data onto the stack during > signal handling: > > https://sourceware.org/bugzilla/

[Bug middle-end/13182] -fstack-check probes too distant when allocating on stack

2017-05-30 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182 --- Comment #7 from Florian Weimer --- (In reply to Eric Botcazou from comment #6) > That's as expected: the probing mechanism maintains a protection area so the > program can recover from a stack overflow condition by raising an exception. > Tha

[Bug middle-end/13182] -fstack-check probes too distant when allocating on stack

2017-05-30 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13182 Eric Botcazou changed: What|Removed |Added Status|NEW |RESOLVED CC|