On Wed, 4 May 2011, Eric Botcazou wrote: > That isn't so easy because fold is invoked on sizes of types by stor-layout.c
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. -- Joseph S. Myers jos...@codesourcery.com
