[Bug libfortran/92836] segfault with inquire()

2020-07-13 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Dominique d'Humieres changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug libfortran/92836] segfault with inquire()

2020-01-24 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Comme

[Bug libfortran/92836] segfault with inquire()

2020-01-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #17 from Janne Blomqvist --- (In reply to Jerry DeLisle from comment #15) > Did we conclude that this is an expected race condition? > > I run the example comment 14 and it just hangs for me. Well, hangs in what sense? For me it ru

[Bug libfortran/92836] segfault with inquire()

2020-01-20 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libfortran/92836] segfault with inquire()

2020-01-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #16 from Thomas Koenig --- (In reply to Jerry DeLisle from comment #15) > Did we conclude that this is an expected race condition? > > I run the example comment 14 and it just hangs for me. It's certainly not mandated to work, but I

[Bug libfortran/92836] segfault with inquire()

2020-01-18 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #15 from Jerry DeLisle --- Did we conclude that this is an expected race condition? I run the example comment 14 and it just hangs for me.

[Bug libfortran/92836] segfault with inquire()

2019-12-08 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #14 from Thomas Koenig --- Created attachment 47441 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47441&action=edit Output of valgrind --tool=helgrind The code from https://gcc.gnu.org/ml/fortran/2019-12/msg00020.html : prog

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #13 from Janne Blomqvist --- To clarify my previous message, instead of inquire(..., exist=exist) if (exist) then open(...) else ! Handle file not existing end if you can do open(..., status='old', iostat=stat) if (stat /= o)

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread abensonca at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #12 from Andrew Benson --- (In reply to Thomas Koenig from comment #11) > (In reply to Andrew Benson from comment #10) > > (In reply to Thomas Koenig from comment #8) > > My reasoning for using INQUIRE to check the existence of the fi

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #11 from Thomas Koenig --- (In reply to Andrew Benson from comment #10) > (In reply to Thomas Koenig from comment #8) > > Also, why do you use inquire at all? AFAIK, it is not an error > > to OPEN a file more than one if you don't ch

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread abensonca at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #10 from Andrew Benson --- (In reply to Thomas Koenig from comment #8) > > No. The inquire() is used only to see if the file exists already. If it > > does, the code branches to read the file, if it does not, the code branches > > to

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #9 from Janne Blomqvist --- (In reply to Thomas Koenig from comment #8) > > No. The inquire() is used only to see if the file exists already. If it > > does, the code branches to read the file, if it does not, the code branches > > to

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Thomas Koenig changed: What|Removed |Added CC||tkoenig at gcc dot gnu.org --- Comment #

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #7 from Tobias Burnus --- (In reply to Jerry DeLisle from comment #3) > character(len=27) :: c > Fortran runtime error: Fortran runtime error: End of recordEnd of record This error I get because 27 characters are not enough — Other

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment #6

[Bug libfortran/92836] segfault with inquire()

2019-12-06 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #5 f

[Bug libfortran/92836] segfault with inquire()

2019-12-05 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #4 from Jerry DeLisle --- Removing close statement: $ ./a.out 0 8 4 2 8 4 -10 5 8 4 4 8 4

[Bug libfortran/92836] segfault with inquire()

2019-12-05 Thread jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org --- Comment

[Bug libfortran/92836] segfault with inquire()

2019-12-05 Thread abensonca at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #2 from Andrew Benson --- Answers to questions raised by Jerry at: https://gcc.gnu.org/ml/fortran/2019-12/msg00059.html > 1) Are you opening a unique file (by file name) in each thread? No. The code is operating on many files, but

[Bug libfortran/92836] segfault with inquire()

2019-12-05 Thread abensonca at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836 --- Comment #1 from Andrew Benson --- Running with -fsanitize=thread (suggested by Tobias) gives: == WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock) (pid=9982) Cycle in lock order graph: M26 (0x7f02bb31c340)