On Tue, Aug 25, 2020 at 08:17:57AM -0600, Jeff Law wrote: > > IOW, don't get too excited by the x1.9 speedup claim. I doubt we'll > > see that in kojki except in niche scenarios where a project's build > > is bottlenecked by a serialization point on compiling one file. > Right. Also note the code isn't accepted upstream yet. I strongly suspect > there's going to be more work required to make what Guiuliano's work ready for > prime time. > > On a positive note, my understanding from talking to Giuliano last year was that > he was trying to parallelize GCC itself which I thought was untractable for a > student project given the amount of unprotected global state. Instead I think he > ended up using the LTO partitioning code to find TU split points, then feeds > those into distinct fork/exec'd copies of GCC which is a much simpler problem to > solve. > > So there may be uses for his work. Obviously the GCC team will continue to > monitor and if/when we think there's a change we should make for Fedora to > exploit Giuliano's work we'll propose it. Yeah. E.g. in the GCC tree itself we have a couple of large generated sources that are known to be parallelization bottlenecks (even if they are started to be compiled as soon as possible, they finish often last), and so instead of enabling it for everything which probably would only slow things down, it might be useful to enable this only for *-match.c, selected insn-*.c and perhaps the libsanitizer asan_interceptors.cpp. Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
