This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/65795] Segfault (invalid write) for ALLOCATE statement involving COARRAYS
- From: "vehre at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 29 Jan 2016 18:35:13 +0000
- Subject: [Bug fortran/65795] Segfault (invalid write) for ALLOCATE statement involving COARRAYS
- Auto-submitted: auto-generated
- References: <bug-65795-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65795
vehre at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vehre at gcc dot gnu.org
--- Comment #2 from vehre at gcc dot gnu.org ---
Investigation shows, that the pseudo code (-fdump-tree-original) is wrong at:
c.caf.data = 0B;
{
integer(kind=4) stat.0;
if (c.caf.data != 0B)
{
stat.0 = 5014;
}
else
{
stat.0 = 0;
c.caf.data = __builtin_malloc (8);
if (c.caf.data == 0B)
{
stat.0 = 5014;
}
}
if (stat.0 == 0)
{
c.caf.dtype = 552;
c.caf.dim[0].lbound = 1;
}
c.caf.x = 0B; ! <<<<<< HERE
if (stat.0 != 0) goto L.1;
L.1:;
stat = stat.0;
.caf has no member x. The component x is from t2 and I assume this line is not
intended, but I had no time yet to figure where it stems from.