> 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
