linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	Nicholas Piggin <npiggin@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: Crash in __do_IRQ with gcc 15
Date: Wed, 14 May 2025 12:06:41 +1000	[thread overview]
Message-ID: <aCP6sXStzfplyvXm@bruin> (raw)
In-Reply-To: <4a2c63a7-4ed2-47c5-b5f7-19e323c267f5@linux.ibm.com>

On Sun, May 11, 2025 at 06:32:25PM +0530, Madhavan Srinivasan wrote:
> 
> Can you try with this patch, I am testing this in my setup.
> 
> Maddy
> 
> 
> diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
> index a0e8b998c9b5..2ce7a4f2b2fb 100644
> --- a/arch/powerpc/kernel/irq.c
> +++ b/arch/powerpc/kernel/irq.c
> @@ -276,7 +276,11 @@ static __always_inline void call_do_irq(struct pt_regs *regs, void *sp)
>                    [callee] "i" (__do_irq)
>                  : // Clobbers
>                    "lr", "xer", "ctr", "memory", "cr0", "cr1", "cr5", "cr6",
> +#if __GNUC__ >= 15
> +                  "cr7", "r0", "r2", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> +#else
>                    "cr7", "r0", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> +#endif
>                    "r11", "r12"
>         );
>  }

That works as long as I have CONFIG_PPC_KERNEL_PCREL enabled, but with
it disabled, it fails to compile.  With PCREL disabled, the kernel
runs just fine without the r2 clobber.  I guess it needs to be:

#if __GNUC__ >= 15 && IS_ENABLED(CONFIG_PPC_KERNEL_PCREL)

or something like that.

Thanks,
Paul.


  reply	other threads:[~2025-05-14  2:06 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 [this message]
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

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=aCP6sXStzfplyvXm@bruin \
    --to=paulus@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).