[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #20 from Janne Blomqvist --- Author: jb Date: Wed Mar 21 18:46:44 2018 New Revision: 258736 URL: https://gcc.gnu.org/viewcvs?rev=258736=gcc=rev Log: PR 84615 Regressions due to type mismatch with character functions Since the kind

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 Janne Blomqvist changed: What|Removed |Added URL||https://gcc.gnu.org/ml/gcc-

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-21 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #18 from Dominique d'Humieres --- > Preliminary tests show that all the failures reported in comment 0 are > fixed by the patch except: > > % gfc -m32 -fdefault-integer-8 >

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-20 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #17 from Dominique d'Humieres --- > Dominique, can you check whether it also fixes the other -fdefault-real-8 -m32 > issues caused by r256284? Preliminary tests show that all the failures reported in comment 0 are fixed by the patch

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-20 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #16 from Janne Blomqvist --- The following patch regtests cleanly on x86_64-pc-linux-gnu, i686-pc-linux-gnu, and successfully passes the #c5 testcase on i686 with -fdefault-real8, and the #c8 testcase on i686 (I didn't test other

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-19 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-19 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #14 from Janne Blomqvist --- (In reply to Thomas Koenig from comment #13) > (In reply to Janne Blomqvist from comment #12) > > So to be clear, the problem seems to be that while the code generation for > > the function itself appears

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #13 from Thomas Koenig --- (In reply to Janne Blomqvist from comment #12) > So to be clear, the problem seems to be that while the code generation for > the function itself appears Ok, it generates the interface wrong (i.e. uses >

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-19 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #12 from Janne Blomqvist --- So to be clear, the problem seems to be that while the code generation for the function itself appears Ok, it generates the interface wrong (i.e. uses the declared charlen kind instead of C_SIZE_T), and

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-19 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #11 from Janne Blomqvist --- Yes, makes sense. And the same happens if one uses an external function with a hand-rolled interface declaration: function chararray2string(chararray) result(text) character(len=1), dimension(:) ::

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-17 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #10 from Dominique d'Humieres --- The following variant without module of the test in comment 8 behaves the same way program TestStringTools character(len=52) :: txt character(len=1), dimension(52) :: chararr = &

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-17 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #9 from Janne Blomqvist --- (In reply to Dominique d'Humieres from comment #8) > Another test that does not require -fdefault-integer-8 > > module chtest > contains > function chararray2string(chararray) result(text) >

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-11 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 --- Comment #8 from Dominique d'Humieres --- Another test that does not require -fdefault-integer-8 module chtest contains function chararray2string(chararray) result(text) character(len=1), dimension(:) :: chararray! input

[Bug fortran/84615] [8 Regression] Executable Segfault for some tests compiled with -m32 after r256284

2018-03-10 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84615 Dominique d'Humieres changed: What|Removed |Added Summary|[8 Regression] Executable |[8 Regression] Executable