[Bug middle-end/83654] -fstack-clash-protection probes below the stack pointer for VLA with constant size

2018-01-03 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83654 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/83654] -fstack-clash-protection probes below the stack pointer for VLA with constant size

2018-01-03 Thread law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83654 --- Comment #3 from Jeffrey A. Law --- Author: law Date: Wed Jan 3 18:22:28 2018 New Revision: 256182 URL: https://gcc.gnu.org/viewcvs?rev=256182&root=gcc&view=rev Log: PR middle-end/83654 * explow.c (anti_adjust_stack_and_probe

[Bug middle-end/83654] -fstack-clash-protection probes below the stack pointer for VLA with constant size

2018-01-02 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83654 --- Comment #2 from Florian Weimer --- I forgot to add a compiler barrier to f2 for the executable test case, so it is not strictly equivalent. With it, valgrind reports: ==375147== Invalid read of size 4 ==375147==at 0x8048403: f2 (in /roo

[Bug middle-end/83654] -fstack-clash-protection probes below the stack pointer for VLA with constant size

2018-01-02 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83654 --- Comment #1 from Florian Weimer --- I forgot to mention that I used “-O2 -fstack-clash-protection”, but there's a valgrind warning with -O0, too.