mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: Arnd Bergmann <arnd@arndb.de>, Kalle Valo <kvalo@kernel.org>
Cc: linux-kernel@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: crosstool: x86 kernel compiled with GCC 14.1 fails to boot
Date: Mon, 08 Jul 2024 17:39:26 -0400	[thread overview]
Message-ID: <a6e0a7d79f9599621a1b4a3263a7b7b5dd810300.camel@sapience.com> (raw)
In-Reply-To: <0ddafa32-1fc2-45e1-b71c-beb64f8cd589@app.fastmail.com>

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

On Mon, 2024-07-08 at 21:03 +0200, Arnd Bergmann wrote:
> On Mon, Jul 8, 2024, at 20:16, Kalle Valo wrote:
> > Hi Arnd,
> > 
> > I installed GCC 14.1 from:
> > 
> > https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_6
> > 4/14.1.0/
> > 
> > But I have a problem that a kernel compiled with that compiler
> > fails to
> > boot on my x86 NUC test box. I don't see any errors, just black
> > screen
...

> 
> 
> Thanks for the report. Unfortunately I have no idea what the
> problem may be, and so far nobody else has reported this.
> 
...

>      Arnd
> 

Another data point in case it's helpful.

I  have been compiling on Archlinux using the native gcc 14.1 toolchain
since early May.

I have had no problems at all booting and running either stable or
mainline on several x86-64 machines including 2 NUCs.
One is NUC6i5SYB and the other is NUC10i5FNK.

  Gene


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-07-08 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 18:16 Kalle Valo
2024-07-08 19:03 ` Arnd Bergmann
2024-07-08 21:39   ` Genes Lists [this message]
2024-07-09  1:57 ` Jeff Johnson
2024-07-09  3:55   ` Jeff Johnson
2024-07-09  5:44     ` Arnd Bergmann
2024-07-09 15:29       ` Jeff Johnson
2024-07-09 16:18         ` Kalle Valo
2024-07-09 19:33         ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a6e0a7d79f9599621a1b4a3263a7b7b5dd810300.camel@sapience.com \
    --to=lists@sapience.com \
    --cc=arnd@arndb.de \
    --cc=ath12k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®