Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #93324 > unrolled thread

Bug#1141885: linux: FTBFS on sh4 due to internal compiler error, works with gcc-16

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1141885: linux: FTBFS on sh4 due to internal compiler error, works with gcc-16 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2026-07-12 11:00 +0200
    Bug#1141885: linux: FTBFS on sh4 due to internal compiler error, works with gcc-16 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2026-07-25 08:10 +0200
    Bug#1141885: marked as done (linux: FTBFS on sh4 due to internal  compiler error, works with wireless stack disabled) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-07-28 07:40 +0200

#93324 — Bug#1141885: linux: FTBFS on sh4 due to internal compiler error, works with gcc-16

Source: linux
Version: 7.1.3-1
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: debian-superh@lists.debian.org
User: debian-superh@lists.debian.org
Usertags: sh4

Hello,

the kernel build on sh4 fails with an internal compiler error as manual builds
have shown. This issue is fixed by updating to at least gcc-16 which contains
a lot of fixes for the GCC SH backend, including a switch to the new register
allocator LRA.

After the switch, GCC may still run out of virtual memory on sh4 when building
large kernel modules, so the kernel config will just have to be adjusted. I'm
currently testing a modified kernel config for sh4 and will report back.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[toc] | [next] | [standalone]

#93447

retitle -1 linux: FTBFS on sh4 due to internal compiler error, works with wireless stack disabled

Hi,

On Sun, 2026-07-12 at 10:58 +0200, John Paul Adrian Glaubitz wrote:
> the kernel build on sh4 fails with an internal compiler error as manual builds
> have shown. This issue is fixed by updating to at least gcc-16 which contains
> a lot of fixes for the GCC SH backend, including a switch to the new register
> allocator LRA.
> 
> After the switch, GCC may still run out of virtual memory on sh4 when building
> large kernel modules, so the kernel config will just have to be adjusted. I'm
> currently testing a modified kernel config for sh4 and will report back.

OK, so I got this sorted out:

(unstable-sh4-sbuild)glaubitz@esk:~/linux-sh4-3$ ls -l linux-image*deb
-rw-r--r-- 1 glaubitz glaubitz 459630732 Jul 24 17:08 linux-image-7.1.4+deb14-sh7751r-dbg_7.1.4-1_sh4.deb
-rw-r--r-- 1 glaubitz glaubitz      1840 Jul 24 17:13 linux-image-7.1.4+deb14-sh7751r_7.1.4-1_sh4.deb
-rw-r--r-- 1 glaubitz glaubitz      1168 Jul 24 17:14 linux-image-sh7751r-dbg_7.1.4-1_sh4.deb
-rw-r--r-- 1 glaubitz glaubitz      1648 Jul 24 17:14 linux-image-sh7751r_7.1.4-1_sh4.deb
(unstable-sh4-sbuild)glaubitz@esk:~/linux-sh4-3$

Disabling the wireless stack is enough. Since we don't use wireless support on sh4
anyway, I will open a pull request shortly pending an additional build test of the
patch.

I've also found a way to resolve the GCC OOM issues on sh4 which I will implement
on all sh4 buildds shortly.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[toc] | [prev] | [next] | [standalone]

#93486 — Bug#1141885: marked as done (linux: FTBFS on sh4 due to internal compiler error, works with wireless stack disabled)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 28 Jul 2026 05:34:52 +0000
with message-id <E1woaSq-0000000DjZI-0LG6@fasolo.debian.org>
and subject line Bug#1141885: fixed in linux 7.2~rc5-1~exp1
has caused the Debian Bug report #1141885,
regarding linux: FTBFS on sh4 due to internal compiler error, works with wireless stack disabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1141885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141885
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web