3 ms·

Mhm. I'm confused. The value of a caching compiler should really become apparent in incremental builds, as in rebuilding after changing a single file. Yet the

Mhm. I'm confused. The value of a caching compiler should really become apparent in incremental builds, as in rebuilding after changing a single file. Yet the author talks about "not seeing any improvements". Like he said, he might be doing something wrong. The speedup observed anyway might come from the compilers having to rebuild/instantiate templated code everytime it's included.

DannyBee 10y ago
"The value of a caching compiler should really become apparent in incremental builds, as in rebuilding after changing a single file. Yet the author talks about "not seeing any improvements"." There are millions of reasons this may not be true in C++. For starters, the use of time and date macros, etc. Without precise dependency tracking of what source lines are dependent on what macros (which is super hard, and i don't think they do), which is not usually what is done (dependency tracking is often much more coarse grained), you may not see an improvement. VisualAge C++ was one of the best incremental C++ implementations i ever saw, and even it did not get to this level.
- pjmlp 10y ago
  > VisualAge C++ was one of the best incremental C++ implementations i ever saw, and even it did not get to this level. How did it compare with Energize C++? I only know both from magazines during those days, even though someone uploaded an Energize video to YouTube. In regards to VisualAge C++ I think only those of us that were active back then can remeber anything about it. Besides the magazines I had with the product review, I never seen much information being posted on the Internet.
  - DannyBee 10y ago
    I never used Energize C++. I remember looking at the code to visualage C++ when i was at ibm about 12 years ago. It was fairly impressive (it built a database of the program with fairly fine grained dependency tracking), at least to younger me. I don't know if people today would have thought it was a mess or not :)

DannyBee 10y ago

"The value of a caching compiler should really become apparent in incremental builds, as in rebuilding after changing a single file. Yet the author talks about "not seeing any improvements"." There are millions of reasons this may not be true in C++. For starters, the use of time and date macros, etc. Without precise dependency tracking of what source lines are dependent on what macros (which is super hard, and i don't think they do), which is not usually what is done (dependency tracking is often much more coarse grained), you may not see an improvement. VisualAge C++ was one of the best incremental C++ implementations i ever saw, and even it did not get to this level.

pjmlp 10y ago
> VisualAge C++ was one of the best incremental C++ implementations i ever saw, and even it did not get to this level. How did it compare with Energize C++? I only know both from magazines during those days, even though someone uploaded an Energize video to YouTube. In regards to VisualAge C++ I think only those of us that were active back then can remeber anything about it. Besides the magazines I had with the product review, I never seen much information being posted on the Internet.
- DannyBee 10y ago
  I never used Energize C++. I remember looking at the code to visualage C++ when i was at ibm about 12 years ago. It was fairly impressive (it built a database of the program with fairly fine grained dependency tracking), at least to younger me. I don't know if people today would have thought it was a mess or not :)