On Mon, 2020-06-08 at 12:21 -0400, Robbie Harwood wrote: > Igor Raits <ignatenkobrain@xxxxxxxxxxxxxxxxx> writes: > > > On Fri, 2020-06-05 at 23:11 -0600, Jeff Law wrote: > > > On Fri, 2020-06-05 at 10:14 +0100, Jonathan Wakely wrote: > > > > On 04/06/20 16:30 -0400, Ben Cotton wrote: > > > > > > > > > https://fedoraproject.org/wiki/Changes/CompilerPolicy > > > > > > > > > > In some ways this means there is no "default" compiler for Fedora. > > > > > The default is whatever the upstream project supports/recommends. > > > > > However, there are probably many packages with upstreams that are > > > > > ambivalent about their compiler choice. For those packages I would > > > > > recommend we keep the status quo at the current time. For a > > > > > package with a dead upstream, the Fedora packager should be able to > > > > > select the compiler they want to use for the package. > > > > > > > > Ideally we'd have CI building (nearly) everything with *both* GCC > > > > and Clang, and finding and fixing problems in packages and in both > > > > compilers. But that's probably not realistic (yet?). > > > > > > You may remember me advocating for this in our meeting in Montreal :- > > > ) So, yea, I'd be totally on board with something like this. I think > > > Tillman was also interested and even floated the idea of finding > > > additional Fedora builder resources to facilitate this kind of > > > scheme. > > > > > > The big problem then becomes getting packagers to address the > > > diagnostics. I've been disappointed at how many packages are > > > ignoring diagnostics (particularly those with security implications) > > > and I'm actively looking at schemes to improve this situation :-) > > > > Just make them error by default and people will have to deal with it > > :) > > (I know you weren't seriously proposing that we do this, but it's an > idea I've seen seriously proposed elsewhere and have experienced.) > > Please do not do this for non-security diagnostics. Supporting this > across a matrix of different compiler versions (and compilers) is truly > awful - especially managing semantics changes between versions, and > pragma stew, and behavior of compilers when asked to ignore flags they > don't understand... My desire is to only target security related diagnostics and quite possibly only a small subset initially. I don't see even trying to move on this until after F33 is done. 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
