This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] variable size arrays in nested functions
- To: rth at redhat dot com
- Subject: Re: [PATCH] variable size arrays in nested functions
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Fri, 9 Feb 01 19:25:11 EST
- Cc: gcc-patches at gcc dot gnu dot org
> How could it be? It seems to me to be semantically critical when you
> need the result of expression that have side-effects.
By using an unnamed VAR_DECL.
But then it's no longer an expression, but a sequence of statements.
> Sure, you can use variables for the bounds, but SAVE_EXPR is just a
> shorthand for that and avoids the scoping issues inherent with such
> variables.
Trading scoping issues for the re-evaluation horrors we have with
SAVE_EXPR and UNSAVE_EXPR is not a win, IMO.
I never did understand UNSAVE_EXPR. What was the motivation for that?