Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-31 Thread Jose R R
On Mon, Oct 31, 2016 at 12:31 AM, Konstantin Demin wrote: > I have tested several scenarios and "KCPPFLAGS=-fno-PIE" does that > trick much better :-) > > -- > SY, > Konstantin Demin uname -a Linux cohuatlicue 4.7.10.tezcatlipoca #1 SMP PREEMPT Mon Oct 31 09:47:07 PDT 2016

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-29 Thread Jose R R
On Tue, Oct 25, 2016 at 3:46 PM, Konstantin Demin wrote: >>> But does this generate the same output as without -enable-default-pie? >>> Some parts of the kernel do use -fpic or -fPIC. Which directive prevails? > > If you call gcc with "-O3 -O0 -O1", only "-O1" option is make

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-25 Thread Konstantin Demin
>> But does this generate the same output as without -enable-default-pie? >> Some parts of the kernel do use -fpic or -fPIC. Which directive prevails? If you call gcc with "-O3 -O0 -O1", only "-O1" option is make sence. See attachments from recent build log (roughly speaking, Linux 4.8.4, "make

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-25 Thread Jörg-Volker Peetz
On Thu, 20 Oct 2016 18:13:05 -0500 "S. R. Wright" wrote: > I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug > fixes should be included, not changes in functionality. In this case > setting enable-default-pie essentially broke backwards compatibility.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread Eric Valette
On 21/10/2016 16:36, Ben Hutchings wrote: On Fri, 2016-10-21 at 12:40 +0300, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. Please revert. It is absolutely supported (so

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread Ben Hutchings
On Fri, 2016-10-21 at 12:40 +0300, Konstantin Demin wrote: > > > > > > > I disagree: you fix debian code but upstream kernel is also affected. > > I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. > > Please revert. > > > $ rmadison linux > linux  | 4.5.5-1   

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread eric2.valette
On 10/21/2016 11:43 AM, Eric Valette wrote: On 10/21/2016 11:40 AM, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread Eric Valette
On 10/21/2016 11:40 AM, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. Please revert. $ rmadison linux linux | 4.5.5-1 | unstable| source

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread Konstantin Demin
>> I disagree: you fix debian code but upstream kernel is also affected. >> I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. >> Please revert. $ rmadison linux linux | 4.5.5-1 | unstable| source linux | 4.5.5-1 |

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-21 Thread Eric Valette
On 10/21/2016 01:45 AM, Konstantin Demin wrote: 2016-10-21 1:49 GMT+03:00 Ben Hutchings : It's a bug when a compiler fails to compile valid code. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Konstantin Demin
2016-10-21 1:49 GMT+03:00 Ben Hutchings : > It's a bug when a compiler fails to compile valid code. > > Ben. > > -- > Ben Hutchings > Never put off till tomorrow what you can avoid all together. Dear Ben, there are no actual bug in compiler, just a caveat to work with it.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread S. R. Wright
I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug fixes should be included, not changes in functionality. In this case setting enable-default-pie essentially broke backwards compatibility. Kernel code that built in -6 failed to build in -7. That, I agree, should be

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Ben Hutchings
On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote: > It's not a GCC bug but kind of new feature. It's a bug when a compiler fails to compile valid code. Ben. > Take a look at this changelog entry: >  gcc-6 (6.2.0-7) unstable; urgency=medium > >    [ Matthias Klose ] >    * Configure

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Konstantin Demin
It's not a GCC bug but kind of new feature. Take a look at this changelog entry: gcc-6 (6.2.0-7) unstable; urgency=medium [ Matthias Klose ] * Configure with --enable-default-pie and pass -z now when pie is enabled; on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.