Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

2016-12-07 Thread Florian Weimer
On 12/07/2016 08:04 AM, Igor Gnatenko wrote: Florian, why only %__global_cflags were changed and not %optflags? Many of packages which don't do %configure, use %optflags. %optflags is for both C and C++. The new flags are meaningless for C++ and apparently accepted by the C++ front end merel

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

2016-12-06 Thread Igor Gnatenko
On Tue, Dec 6, 2016 at 9:01 AM, Florian Weimer wrote: > On 12/06/2016 08:27 AM, Ralf Corsepius wrote: >> >> On 12/06/2016 04:44 AM, Orion Poplawski wrote: >> >>> I've run into a reasonable number of failures of (custom) configure >>> checks due to this. Mainly calling exit() without including std

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

2016-12-06 Thread Florian Weimer
On 12/06/2016 08:27 AM, Ralf Corsepius wrote: On 12/06/2016 04:44 AM, Orion Poplawski wrote: I've run into a reasonable number of failures of (custom) configure checks due to this. Mainly calling exit() without including stdlib.h. So keep alert everyone. Unfortunately this can lead to unpredi

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

2016-12-05 Thread Ralf Corsepius
On 12/06/2016 04:44 AM, Orion Poplawski wrote: I've run into a reasonable number of failures of (custom) configure checks due to this. Mainly calling exit() without including stdlib.h. So keep alert everyone. Unfortunately this can lead to unpredictable and perhaps hard to detect changes. It

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-12-05 Thread Thomas Daede
I have such a piece of hardware and could run a benchmark in ~1 week, if you're curious. That said, Fedora Workstation is borderline unusable on that hardware anyway - due to the integrated graphics, not the CPU. I doubt most users would notice a slowdown from different CFLAGS when gnome-shell can'

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

2016-12-05 Thread Orion Poplawski
On 11/10/2016 03:30 AM, Jan Kurik wrote: = Proposed System Wide Change: Fedora 26 C/C++ Compilation Flags Updates = https://fedoraproject.org/wiki/Changes/Fedora26CFlags Change owner(s): * Florian Weimer This change updates the default C/C++ compilation flags, as determined by the redhat-rpm-c

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-13 Thread Xose Vazquez Perez
Dan Horák wrote: > We are going to change the default -mcpu for s390(x) from the current > -mcpu=z9-109 to -mcpu=z10. z10 is the minimum level various projects > require - llvm/clang, OCaml, pypy3, ... Unfortunately we can't go > higher because our community guest VM is still running on a z10 mach

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-13 Thread Dan Horák
On Thu, 10 Nov 2016 11:30:47 +0100 Jan Kurik wrote: > = Proposed System Wide Change: Fedora 26 C/C++ Compilation Flags > Updates = https://fedoraproject.org/wiki/Changes/Fedora26CFlags > > Change owner(s): > * Florian Weimer > > This change updates the default C/C++ compilation flags, as deter

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-11 Thread Kevin Kofler
Neal Gompa wrote: > They *could* if people built 32-bit UEFI loader stuff for it. And > there have been efforts in the past for it. I wouldn't completely rule > this out, though it is uncommon. 32-bit grub2-efi is actually available. You should be able to install on 32- bit UEFI with Calamares, if

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-10 Thread Florian Weimer
On 11/10/2016 12:49 PM, Neal Gompa wrote: On Thu, Nov 10, 2016 at 5:30 AM, Jan Kurik wrote: but many current Atom-based devices cannot run Fedora because Fedora does not support their 32-bit UEFI boot environment. They *could* if people built 32-bit UEFI loader stuff for it. And there have be

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-10 Thread Florian Weimer
On 11/10/2016 12:42 PM, Alexander Ploumistos wrote: On Thu, Nov 10, 2016 at 12:30 PM, Jan Kurik wrote: * Drop -mtune=atom on i686: This flag was added to improve performance on the Intel Bonnell microarchitecture. Would you happen to have a ballpark estimate of the performance cost that would

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-10 Thread Neal Gompa
On Thu, Nov 10, 2016 at 5:30 AM, Jan Kurik wrote: > but many current Atom-based > devices cannot run Fedora because Fedora does not support their 32-bit > UEFI boot environment. They *could* if people built 32-bit UEFI loader stuff for it. And there have been efforts in the past for it. I wouldn'

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-10 Thread Alexander Ploumistos
On Thu, Nov 10, 2016 at 12:30 PM, Jan Kurik wrote: > * Drop -mtune=atom on i686: This flag was added to improve performance > on the Intel Bonnell microarchitecture. Would you happen to have a ballpark estimate of the performance cost that would incur on actual Bonnel CPUs? __

F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates

2016-11-10 Thread Jan Kurik
= Proposed System Wide Change: Fedora 26 C/C++ Compilation Flags Updates = https://fedoraproject.org/wiki/Changes/Fedora26CFlags Change owner(s): * Florian Weimer This change updates the default C/C++ compilation flags, as determined by the redhat-rpm-config package. == Detailed Description =