Re:Four more carmakers join diesel emissions row
by function_seven on Friday October 09, 2015 @09:21PM
(#10364085)
Imagine a compiler that recognizes when you're attempting to compile Firefox from source. It checks your internet connection speed and hashes all the source files. If your Internet connection is sufficient, and the hashes match, this nifty compiler would "optimize" the compilation by downloading the matching binary from mozilla.org.
[ Parent
| on HN ]
Re:Four more carmakers join diesel emissions row
by kazinator on Friday October 09, 2015 @09:51PM
(#10364157)
ccache hashes the preprocessed input to gcc, hashes it, and pulls out a previously compiled object file if possible. You can use it together with distcc to farm out jobs to other machines; whether you pick their caches or yours depends on the order of ccache and distcc on the command line.
Re:Four more carmakers join diesel emissions row
by wlievens on Saturday October 10, 2015 @03:42AM
(#10364837)
So basically any caching strategy?
Compiler optimisation isnt about compiling faster, though :-)
Re:Four more carmakers join diesel emissions row
by throwupaway1138 on Saturday October 10, 2015 @07:14AM
(#10365159)
Of course it is, at least if the optimized compiler is compiled with an optimized compiler, but also generally fast compilation is optimal.
Re:Four more carmakers join diesel emissions row
by wlievens on Saturday October 10, 2015 @08:19AM
(#10365285)
Fast compilation is a worth goal, but it's not fundamentally different from optimizing other kinds of programs: it involves good selection of data structures and algorithms, smart caching, that sort of stuff.
Compiler optimization (in the sense of optimizing the emitted code) is a research area of its own with millions of man hours invested.