[prev in list] [next in list] [prev in thread] [next in thread]
List: gcc-bugs
Subject: [Bug fortran/42958] Weird temporary array allocation
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla () gcc ! gnu ! org>
Date: 2019-03-31 16:44:37
Message-ID: bug-42958-4-xI6BwzfgM3 () http ! gcc ! gnu ! org/bugzilla/
[Download RAW message or body]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42958
--- Comment #26 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #25)
> > If you find anything still missing in the library, please let me know.
> > I thought I had converted everything to the macros, which are fairly
> > easy to change, but I may be mistaken.
>
> Is there anything left? or could this PR be closed as FIXED?
We still do
{
if ((real(kind=4)[0:] * restrict) a.data != 0B)
{
__builtin_free ((void *) a.data);
(real(kind=4)[0:] * restrict) a.data = 0B;
}
}
Also, we have space array descriptor fields now, so for GCC 10, we
can finally implement the "allocated" flag.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic