On Thu, 4 Jun 2020 16:30:09 -0400 Ben Cotton <bcotton@xxxxxxxxxx> wrote: > https://fedoraproject.org/wiki/Changes/CompilerPolicy > An obvious example is Firefox. Upstream, the Firefox project builds > primarily with Clang/LLVM. Yet we force the Fedora package owner to > find and fix issues building with GCC then either carry those custom > fixes forward in Fedora or negotiate with upstream to get those > changes upstreamed. While this process can be helpful in finding > non-portable code, this is ultimately a poor use of the packager's > time. I compile firefox nightly locally from an hg repository. What I notice is that although mozilla officially states that it is possible to limit resource use, even though I set a maximum thread count, or maximum load, the clang compiler grabs every core and maxes it out to 100%. Will this change help with that? i.e. is this a clang problem? Or is my experience because of a problem with the firefox compilation process? Thanks. _______________________________________________ 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
