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] PR20541 - allocatable components (TR15541)

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: Paul Thomas <paulthomas2 at wanadoo dot fr>
Cc: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
Date: Sun, 08 Oct 2006 13:14:47 +0200
Subject: Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
References: <452490A3.4000102@wanadoo.fr> <20061005185239.a2tqyiz81wc8w8cs@webmail.physik.uni-muenchen.de> <4525DC86.6050504@wanadoo.fr>

Tobias,

Out of curiousity, why didn't you use alloca instead of doing all this bookkeeping? Maybe because you would have needed bookkeeping anyway for the case where the allocatable component would have been > -fmax-stack-var-size? Or is there a simpler reason?

Ignorance.

I was going back through the correspondence, getting ready for tomorrow morning's commit, when I saw this.

I was speaking for myself here! Erik might well have known all about it and had cogent reasons for not using it.

Cheers

Paul

Follow-Ups:
- Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
  - From: Erik Edelmann

References:
- [Patch, fortran] PR20541 - allocatable components (TR15541)
  - From: Paul Thomas
- Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
  - From: Tobias Schlüter
- Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
  - From: Paul Thomas

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