This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
- From: Paul Thomas <paulthomas2 at wanadoo dot fr>
- To: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
- Cc: "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 06 Oct 2006 06:33:10 +0200
- Subject: Re: [Patch, fortran] PR20541 - allocatable components (TR15541)
- References: <452490A3.4000102@wanadoo.fr> <20061005185239.a2tqyiz81wc8w8cs@webmail.physik.uni-muenchen.de>
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.
Having looked at the spec. for alloca, you are right, we would have had
to branch for > -fmax-stack-var-size; otherwise the warnings in the gcc
manual would hold good. I will put a TODO in the code somewhere.
It would simplify the code considerably - take a look for some of the
testcases!
Good idea
Thanks