Re: middle-end/10415: allocated stack space non optimimal

[Wolfgang Bangerth <bangerth@ices.utexas.edu>]

The following reply was made to PR middle-end/10415; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: GrzegorzB <b.grzes@interia.pl>
Cc: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>
Subject: Re: middle-end/10415: allocated stack space non optimimal
Date: Tue, 15 Apr 2003 15:15:25 -0500 (CDT)

 > Program test.c:
 > 
 > void f() {
 > 	char buf[3];
 > }
 > 
 > main() {
 > 	f();
 > }
 > 
 > I compile this:
 > gcc -S -o test test.c
 
 What happens if you switch on optimization? Is stack allocation better 
 then?
 
 [I think that the compiler will just optimize away everything in that 
 case, but you might prevent this by doing something like
 
 void p(char *x);
 void f() {
   char buf[3];
   p(buf);
 }
 
 and simply not defining f().]
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/