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: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Richard Guenther <richard dot guenther at gmail dot com>, Xinliang David Li <davidxl at google dot com>, Jan Hubicka <hubicka at ucw dot cz>
- Date: Wed, 4 May 2011 12:29:28 +0200
- Subject: Re: [google]: initialize language field for clone function struct
- References: <BANLkTimaZh7CjWiSDoHmd9FJjz9qipwM7g@mail.gmail.com> <201105041200.29307.ebotcazou@adacore.com> <Pine.LNX.4.64.1105041013350.25186@digraph.polyomino.org.uk>
> That's what we should phase out. The eventual aim should be for (a)
> folding on GIMPLE (gimple-fold etc. - working with SSA not combined trees)
> as an optimization and (b) folding done by front ends only when required
> for language semantics (e.g. constant expressions). If you want to
> optimize type sizes, look at where they are located in the GIMPLE IR, as a
> property of the IR rather than as a hook checking global state.
In Ada we simply don't want to emit raw type sizes in the GIMPLE IR, they are
just too heavy to be manipulated up to there, even for moderately complex
code. That's why we need them to be folded as soon as possible, and even
factored out of the GENERIC IR into functions when they are self-referential.
--
Eric Botcazou