From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: LEROY Christophe <christophe.leroy2@cs-soprasteria.com>,
Nicholas Piggin <npiggin@gmail.com>,
Paul Mackerras <paulus@ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Crash in __do_IRQ with gcc 15
Date: Sat, 24 May 2025 13:34:08 -0500 [thread overview]
Message-ID: <20250524183408.GU30295@gate.crashing.org> (raw)
In-Reply-To: <233701f4-4d31-40b6-97d3-5abd8b9954ab@app.fastmail.com>
On Mon, May 19, 2025 at 04:05:05PM +0200, Arnd Bergmann wrote:
> On Tue, May 13, 2025, at 12:08, Arnd Bergmann wrote:
> > On Mon, May 12, 2025, at 20:13, LEROY Christophe wrote:
> >> Hi Arnd,
> >>
> >> Do you know when you will be able to add GCC 15 to
> >> https://mirrors.edge.kernel.org/pub/tools/crosstool/ ?
> >
> > I have to create a new build environment for gcc-15 after I lost
> > access to the machine I used for the earlier builds. I should
> > be able to do that within a few weeks, but unfortunately it's
> > a little more work than just rerunning my scripts (which I still
> > have).
>
> I've uploaded gcc-15.1 binaries now. I've only tested the arm64,
> as usual, so please let me know if the powerpc and x86 hosted
> ones cause any problems.
As always: thank you!
Segher
prev parent reply other threads:[~2025-05-24 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 1:35 Crash in __do_IRQ with gcc 15 Paul Mackerras
2025-05-11 13:02 ` Madhavan Srinivasan
2025-05-14 2:06 ` Paul Mackerras
2025-05-21 12:56 ` LEROY Christophe
2025-05-12 3:31 ` Michael Ellerman
2025-05-13 12:27 ` Paul Mackerras
2025-05-13 16:31 ` Segher Boessenkool
2025-05-12 18:13 ` LEROY Christophe
2025-05-13 10:08 ` Arnd Bergmann
2025-05-19 14:05 ` Arnd Bergmann
2025-05-24 18:34 ` Segher Boessenkool [this message]
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=20250524183408.GU30295@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy2@cs-soprasteria.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.