Re:Optimizing the unoptimizable: a journey to faster C++ com...
by vitaut on Sunday January 07, 2024 @05:35PM
(#38905916)
Unfortunately the std module alone doesn't help much because 1 second is 3x slower than before the optimization described in the post but maybe more fine-grained modules will (or if std module import made faster).
Re:Optimizing the unoptimizable: a journey to faster C++ com...
by pjmlp on Monday January 08, 2024 @02:02AM
(#38909009)
For the whole library, everything.
Also Microsof Office team has been migrating to modules, with great build improvements.
Re:Optimizing the unoptimizable: a journey to faster C++ com...
by za3faran on Monday January 08, 2024 @09:36AM
(#38912487)
Any place where I can read up more about this?
Re:Optimizing the unoptimizable: a journey to faster C++ com...
by pjmlp on Monday January 08, 2024 @09:57AM
(#38912822)
https://devblogs.microsoft.com/cppblog/integrating-c-header-...
https://devblogs.microsoft.com/cppblog/integrating-c-header-...
Key takeway
"Fortunately, we were able to show a build performance improvement great enough that the team agreed to adopt header units into the Office production build system alongside msvc 17.6.6!"
Unfortunely the performance findings blogpost is still WIP.
Re:Optimizing the unoptimizable: a journey to faster C++ com...
by OskarS on Monday January 08, 2024 @03:37AM
(#38909500)
Not to be "that guy", but... one second is a VERY VERY long time to compile a hello world program.
EDIT:
This compiles in 1 second on an i7 laptop.