This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Question on internal_get_tmp_var
- From: Richard Henderson <rth at redhat dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 23 Jun 2004 15:37:46 -0700
- Subject: Re: Question on internal_get_tmp_var
- References: <10406232227.AA21880@vlsi1.ultra.nyu.edu>
On Wed, Jun 23, 2004 at 06:27:13PM -0400, Richard Kenner wrote:
> I'm not quite sure I understand what "1)" in front of the function means
> or why it claims it can't be used for SAVE_EXPR, but it is indeed used
> for SAVE_EXPR.
The comment actually applies to get_formal_tmp_var, not to
internal_get_tmp_var. Tsk, tsk, Jason.
> Also, why isn't TREE_READONLY set on such a variable?
TREE_READONLY for scalar values doesn't help anything. I wouldn't
have expected this to get used for aggregates very often.
> Finally, is there any good reason why DECL_INITIAL couldn't be set to the
> initializing value?
DECL_INITIAL isn't gimple. Notice that we *clear* DECL_INITIAL
in gimplify_decl_stmt.
r~