This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [google]: initialize language field for clone function struct
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Xinliang David Li <davidxl at google dot com>, Jan Hubicka <hubicka at ucw dot cz>
- Date: Thu, 5 May 2011 12:07:51 +0200
- Subject: Re: [google]: initialize language field for clone function struct
- References: <BANLkTimaZh7CjWiSDoHmd9FJjz9qipwM7g@mail.gmail.com> <201105051123.34184.ebotcazou@adacore.com> <BANLkTikGBurBXmG1x29RX9QauAJdWPemnA@mail.gmail.com>
> But where do you expand it without the SAVE_EXPR? The same
> restrictions apply there. So I suppose you expand it to a function
> in which case there is the context where the SAVE_EXPR can be
> expanded exactly once.
You don't have SAVE_EXPRs so you're precisely controlling what you're doing.
Once a SAVE_EXPR is generated, things are pretty much out of control for the
front-end.
> But maybe I'm confused and simply lack an actual testcase that
> shows the issue ;)
Remove the call to global_bindings_p from variable_size and run gnat.dg.
--
Eric Botcazou