https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62094
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Mon, Aug 11, 2014 at 07:17:15PM +0000, sham at Central dot UH.EDU wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62094 > > --- Comment #2 from sham at Central dot UH.EDU --- > Thanks, Steve. My pick of libgfortran as "product line" was because > it was the closest from the limited choices that the bug report form > offered. > > As you observed, this is probably just a LIBC bug. On the other hand, > I do not know the interconnections between the code generated for > ALLOCATE/DEALLOCATE by GFortran and the conventions governing call > to malloc()/free(). > glibc is developed independently of gcc. You can go to http://www.gnu.org/software/libc/bugs.html for more information on reporting glibc bugs. Unofortunately, I suspect the glibc developers will want a C program that exposes the problem not a Fortran program.
