[Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast

2021-12-19 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437 Andrew Pinski changed: What|Removed |Added Resolution|--- |WORKSFORME Status|WAITING

[Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast

2021-12-19 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437 --- Comment #4 from Andrew Pinski --- I tried "-Ofast -fmax-stack-var-size=2096" and I get: _38 = __builtin_malloc (848); Without the max-stack-var-size option, I get: real(kind=8) A.22[106]; Even with " -fmax-stack-var-size=2096

[Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast

2018-07-09 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437 --- Comment #3 from janus at gcc dot gnu.org --- (In reply to janus from comment #2) > (In reply to Dominique d'Humieres from comment #1) > > WORKSFORME. AFAIR -Ofast implies -fstack-arrays. > > Yeah, right, -fstack-arrays is the crucial flag her

[Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast

2018-07-09 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437 --- Comment #2 from janus at gcc dot gnu.org --- (In reply to Dominique d'Humieres from comment #1) > WORKSFORME. AFAIR -Ofast implies -fstack-arrays. Yeah, right, -fstack-arrays is the crucial flag here. > What is the output of > > ulimit -s

[Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast

2018-07-09 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|