On Fri, 2020-06-05 at 14:11 +0000, devel-request@xxxxxxxxxxxxxxxxxxxxxxx wrote: > Date: Fri, 5 Jun 2020 14:16:58 +0100 > > From: Ian McInerney <Ian.S.McInerney@xxxxxxxx> > > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy > > Change > > To: Development discussions related to Fedora > > <devel@xxxxxxxxxxxxxxxxxxxxxxx> > > Message-ID: > > <CACp=VfYoTukjb6bsgj2KGOTrdgHQvSn_XDQV2bwxJ+zVVP4T3w@xxxxxxxxxxxxxx> > > Content-Type: multipart/alternative; > > boundary="0000000000001b547505a756148e" > > > > --0000000000001b547505a756148e > > Content-Type: text/plain; charset="UTF-8" > > > > On Fri, Jun 5, 2020 at 1:51 PM Stephan Bergmann <sbergman@xxxxxxxxxx> wrote: > > > > > On 05/06/2020 10:15, Frantisek Zatloukal wrote: > > > [...] Apart from > > > browsers, LibreOffice is going to use LLVM/Clang from Release 7.0 too, > > > so that would potentially be another added work to LibreOffice packagers > > > in the future. > > Just to clarify, upstream LibreOffice supports both GCC and Clang on > > Linux equally well since ~forever, and there is no change coming for LO > > 7.0 that I'm aware of. Upstream Linux binaries are built with GCC, FWIW. > > > I think what they are referring to is that there was a patch [1] a few > > months ago making Clang *preferred* for building the LibreOffice > > rendering code in response to a slow-performance bug [2]. This highlights what I consider probably the most interesting case. Upstream has a preference for Liberoffice (Clang/LLVM), but supports both Clang/LLVM and GCC. In this case I think Fedora policy should be to follow the upstream preference. Jeff > _______________________________________________ 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
