GCC 15 and stable kernels

GCC 15 and stable kernels

[Chris Clayton]

Hi Greg,

I've built the four stable kernels that were released on 25 April. I found that to successfully build with GCC-15, each
of them required backports of one or both of two upstream commits. Those commits are:

Title		Commit						Author	
nonstring 	9d7a0577c9db35c4cc52db90bc415ea248446472  	Linus
gnu11		b3bee1e7c3f2b1b77182302c7b2131c804175870	Alexey Dobriyan

6.14.4 and 6.12.25 required only nonstring. 6.6.87 required only gnu11, 6.1.35 required both.

Additionally, chasing down why my new Bluetooth mouse doesn't work, I also had cause to build 5.15.180 and found that it
needed gnull.

I have TO dash out now, but I could send you a zip archive of the patches later today, if that would help.

Chris

Re: GCC 15 and stable kernels

[Greg Kroah-Hartman]

On Mon, Apr 28, 2025 at 12:14:09PM +0100, Chris Clayton wrote:
> Hi Greg,
> 
> I've built the four stable kernels that were released on 25 April. I found that to successfully build with GCC-15, each
> of them required backports of one or both of two upstream commits. Those commits are:
> 
> Title		Commit						Author	
> nonstring 	9d7a0577c9db35c4cc52db90bc415ea248446472  	Linus
> gnu11		b3bee1e7c3f2b1b77182302c7b2131c804175870	Alexey Dobriyan
> 
> 6.14.4 and 6.12.25 required only nonstring. 6.6.87 required only gnu11, 6.1.35 required both.
> 
> Additionally, chasing down why my new Bluetooth mouse doesn't work, I also had cause to build 5.15.180 and found that it
> needed gnull.
> 
> I have TO dash out now, but I could send you a zip archive of the patches later today, if that would help.

Please send backported patches of the above, as they do not apply
cleanly as-is, and we will be glad to review and apply them.

thanks,

greg k-h

Re: GCC 15 and stable kernels

[Chris Clayton]

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On 28/04/2025 12:22, Greg Kroah-Hartman wrote:
> On Mon, Apr 28, 2025 at 12:14:09PM +0100, Chris Clayton wrote:
>> Hi Greg,
>>
>> I've built the four stable kernels that were released on 25 April. I found that to successfully build with GCC-15, each
>> of them required backports of one or both of two upstream commits. Those commits are:
>>
>> Title		Commit						Author	
>> nonstring 	9d7a0577c9db35c4cc52db90bc415ea248446472  	Linus
>> gnu11		b3bee1e7c3f2b1b77182302c7b2131c804175870	Alexey Dobriyan
>>
>> 6.14.4 and 6.12.25 required only nonstring. 6.6.87 required only gnu11, 6.1.35 required both.
>>
>> Additionally, chasing down why my new Bluetooth mouse doesn't work, I also had cause to build 5.15.180 and found that it
>> needed gnull.
>>
>> I have TO dash out now, but I could send you a zip archive of the patches later today, if that would help.
> 
> Please send backported patches of the above, as they do not apply
> 

The patches are in the attached tarball.

cleanly as-is, and we will be glad to review and apply them.
> 
> thanks,
> 
> greg k-h

[-- Attachment #2: backported-gcc15-patches.tar.xz --]
[-- Type: application/x-xz, Size: 1516 bytes --]

Re: GCC 15 and stable kernels

[Greg Kroah-Hartman]

On Mon, Apr 28, 2025 at 04:08:27PM +0100, Chris Clayton wrote:
> On 28/04/2025 12:22, Greg Kroah-Hartman wrote:
> > On Mon, Apr 28, 2025 at 12:14:09PM +0100, Chris Clayton wrote:
> >> Hi Greg,
> >>
> >> I've built the four stable kernels that were released on 25 April. I found that to successfully build with GCC-15, each
> >> of them required backports of one or both of two upstream commits. Those commits are:
> >>
> >> Title		Commit						Author	
> >> nonstring 	9d7a0577c9db35c4cc52db90bc415ea248446472  	Linus
> >> gnu11		b3bee1e7c3f2b1b77182302c7b2131c804175870	Alexey Dobriyan
> >>
> >> 6.14.4 and 6.12.25 required only nonstring. 6.6.87 required only gnu11, 6.1.35 required both.
> >>
> >> Additionally, chasing down why my new Bluetooth mouse doesn't work, I also had cause to build 5.15.180 and found that it
> >> needed gnull.
> >>
> >> I have TO dash out now, but I could send you a zip archive of the patches later today, if that would help.
> > 
> > Please send backported patches of the above, as they do not apply
> > 
> 
> The patches are in the attached tarball.

Please submit them as a proper patch, with the original changelog and
authorship information intact.  We have thousands of examples of this on
the stable mailing list for how this should be done.

thanks,

greg k-h