This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work

From: Tobias Burnus <burnus at net-b dot de>
To: Andrew Pinski <pinskia at gmail dot com>
Cc: Paul Thomas <paulthomas2 at wanadoo dot fr>, Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 14 Mar 2007 20:20:55 +0100
Subject: Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
References: <45F7967A.50203@wanadoo.fr> <45F7B8D5.5010805@net-b.de> <de8d50360703141211x1bea2bebw890d885204867015@mail.gmail.com>

Andrew Pinski wrote:
> On 3/14/07, Tobias Burnus <burnus@net-b.de> wrote:
>>   static struct foo t = {};
>>   if ((real4[0:] *) t.x.data != 0B)
> The t variable is still zero initialized as defined by either {} or by
> the case of being a static variable.
That means we could optimize

  static struct foo_type f_a = {.mv={.data=0B}};

to

  static struct foo_type f_a = {};

for pointers?


Tobias

References:
- [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
  - From: Paul Thomas
- Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
  - From: Tobias Burnus
- Re: [Patch, fortran] PR31163 - SAVEd derived types with ALLOCATABLE components don't work
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]