This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
- From: Tobias Burnus <burnus at net-b dot de>
- To: Paul Thomas <paulthomas2 at wanadoo dot fr>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 14 Mar 2007 09:56:53 +0100
- Subject: Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
- References: <45F7967A.50203@wanadoo.fr>
Paul,
Paul Thomas wrote:
> This is obvious but I submit it for review anyway:)
I think this is ok, but I have a question, where does *.data get
initialized to zero? It seems to work correctly (including valgrind
check), but I somehow miss in the tree something like for pointers:
static struct foo_type f_a = {.mv={.data=0B}};
The tree is for allocatable is:
static struct foo t = {};
if ((real4[0:] *) t.x.data != 0B)
> PS Note that since Tobias' fix, c_by_val_1.f fails on Cygwin_NT
Do you know which part fails (real(8), integer(8), complex(8) or even
something else)? Unless, we find something which works on all platforms,
we have to wait for kind=c_double, c_int64_t and c_complex_double :-(
Tobias