This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Group static constructors and destructors in specific subsections


On 10/15/2010 06:16 PM, Jan Hubicka wrote:
> We still have isue with including iostream causing static constructor that is bit careless.  Now hever the constructors will all sit in the same section that will be paged in quite effecitvely at startup.  Chrome is told to have about 1300 of such constructors, so it will account from few extra KB at startup read in sequence, but backward.  Should not be disasterous, still something more effective would be nice.
>   
Yes, I meant exactly the <iostream> case. I seem to remember that we
came to the conclusion that it's hard to do it very differently at the
library level, because the letter of the standard is pretty close to
what we have been doing. Nice to see that we are making progress thanks
to generic improvements.

Paolo.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]