RE: Extending functionality of -frepo

2005-09-08 Thread Noe Aljaz ITICMN
> > Even when using precompiled headers, .pch files can get pretty big, > > and they must still be loaded, > > They do? Odd, on my platform, we only mmap them. If one > doesn't touch them (and nothing else near them), they aren't > loaded for me. > > > which takes time. > > mmap is fairly qu

Re: Extending functionality of -frepo

2005-09-07 Thread Mike Stump
On Sep 7, 2005, at 12:36 AM, Noe Aljaz ITICMN wrote: Maybe... I think the 'big_header', which is required by template definitions, has a big impact here. And I find it hard to believe that excluding a big chunk of code from compilation results in no speed-up. Even when using precompiled headers,

RE: Extending functionality of -frepo

2005-09-07 Thread Noe Aljaz ITICMN
> Normal compiles instantiate items as determined by the > database. It is a known waste of compile time to not so > instantiate such things, as we know they will be > instantiated. So, the entire concept doesn't make much sense > to me, unless you only are only interested in the speedup > f

Re: Extending functionality of -frepo

2005-09-06 Thread Mike Stump
On Sep 5, 2005, at 12:09 AM, Noe Aljaz ITICMN wrote: 2. Define macro NO_TEMPLATE_INSTANTIATION during normal compilation and un-define it when g++ is called by collect2, and making this accessible via some new compiler option (e.g. - frepo2)? Why would this be good? Normal compiles instan