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(). N. Shamsundar ________________________________________ From: kargl at gcc dot gnu.org [gcc-bugzi...@gcc.gnu.org] Sent: Monday, August 11, 2014 1:47 PM To: shamsun...@uh.edu Subject: [Bug libfortran/62094] Program crash when executing DEALLOCATE with addresses that have 0 in bits 26 and higher (little-endian) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62094 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #1 from kargl at gcc dot gnu.org --- Looks like a bug in glibc exposed by gfortran. Not sure why you think that this is a libgfortran bug. -- You are receiving this mail because: You reported the bug.