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


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

Using GCC 10 for all architectures

Started byBastian Blank <waldi@debian.org>
First post2020-08-04 16:20 +0200
Last post2020-08-05 20:00 +0200
Articles 3 — 2 participants

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


Contents

  Using GCC 10 for all architectures Bastian Blank <waldi@debian.org> - 2020-08-04 16:20 +0200
    Re: Using GCC 10 for all architectures Alper Nebi Yasak <alpernebiyasak@gmail.com> - 2020-08-05 11:40 +0200
      Re: Using GCC 10 for all architectures Alper Nebi Yasak <alpernebiyasak@gmail.com> - 2020-08-05 20:00 +0200

#67684 — Using GCC 10 for all architectures

FromBastian Blank <waldi@debian.org>
Date2020-08-04 16:20 +0200
SubjectUsing GCC 10 for all architectures
Message-ID<AA5Xk-YY-7@gated-at.bofh.it>
Hi folks

I'll bump the compiler version to GCC 10 on the master branch soonish,
i.e. for 5.8 and later kernel versions.  If there are any supported
architectures where GCC 10 is known to cause regressions, this can be
reverted *temporarily* for those architectures, but needs to be fixed
for the Bullseye release.

Regards,
Bastian

-- 
Spock: The odds of surviving another attack are 13562190123 to 1, Captain.

[toc] | [next] | [standalone]


#67701

FromAlper Nebi Yasak <alpernebiyasak@gmail.com>
Date2020-08-05 11:40 +0200
Message-ID<AAo3T-3wH-13@gated-at.bofh.it>
In reply to#67684
On 04/08/2020 16:59, Bastian Blank wrote:
> I'll bump the compiler version to GCC 10 on the master branch soonish,
> i.e. for 5.8 and later kernel versions.  If there are any supported
> architectures where GCC 10 is known to cause regressions, this can be
> reverted *temporarily* for those architectures, but needs to be fixed
> for the Bullseye release.

When I build an arm64 kernel with upstream v5.8 (make bindeb-pkg) on 
sid, the built kernel can't load any modules -- lsmod output is empty, 
modprobe-ing any module fails with "Exec format error". I think it might 
be related to GCC 10, because I had also tried building the Debian 
package when you just updated it to v5.8 (eebcb7ad) and got a fully 
working kernel then (but the overall build failed due to udebs which you 
already fixed).

I also ran into a GCC issue other people already reported [1][2] while 
building the current version of the master branch (26a6ecc2) for arm64 
(I wanted to check if it could load modules correctly, I will send an 
update if I can manage to test that).

[1] https://lkml.org/lkml/2020/7/27/575
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377

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


#67704

FromAlper Nebi Yasak <alpernebiyasak@gmail.com>
Date2020-08-05 20:00 +0200
Message-ID<AAvRL-89R-1@gated-at.bofh.it>
In reply to#67701
On 05/08/2020 12:36, Alper Nebi Yasak wrote:
> When I build an arm64 kernel with upstream v5.8 (make bindeb-pkg) on
> sid, the built kernel can't load any modules -- lsmod output is empty,
> modprobe-ing any module fails with "Exec format error". I think it might
> be related to GCC 10, 

This doesn't happen on the Debian package even with GCC 10. Maybe 
something went wrong with my config or environment with the upstream builds.

> I also ran into a GCC issue other people already reported [1][2] while
> building the current version of the master branch (26a6ecc2) for arm64
> (I wanted to check if it could load modules correctly, I will send an
> update if I can manage to test that).
> 
> [1] https://lkml.org/lkml/2020/7/27/575
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377

There is a "quick workaround" suggested in [2], and applying it does fix 
the arm64 build.

[toc] | [prev] | [standalone]


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


csiph-web