[Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92621 --- Comment #7 from Michael Briggs --- Comment on attachment 49834 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49834 fortran portion of test case First part of a two part test case, Fortran & C. The bug appears as: malloc: *** error for object 0x7fff695a8eb8: pointer being freed was not allocated The problem is observed in gcc/gfortran 9.3.0 and 10.2.0 If the intent of "array" is changed from "out" to "inout" the program runs without any problem.
[Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92621 --- Comment #6 from Michael Briggs --- Comment on attachment 49834 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49834 fortran portion of test case An additional test case, in two parts: Fortran & C. The bug appears as: malloc: *** error for object 0x7fff695a8eb8: pointer being freed was not allocated The problem is observed for gcc/gfortran 9.3.0 and 10.2.0 If the intent of "array" is changed from "out" to "inout" the program runs without any problem.
[Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92621 --- Comment #5 from Michael Briggs --- Created attachment 49835 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49835=edit C portion of test case The second part of an additional test case.
[Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92621 Michael Briggs changed: What|Removed |Added CC||briggs.michaels at gmail dot com --- Comment #4 from Michael Briggs --- Created attachment 49834 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49834=edit fortran portion of test case