[issue report] ARM: compile error of frame size

[Geert Uytterhoeven]

Hi Arnd,

On Wed, 15 Oct 2025 at 13:03, Arnd Bergmann <arnd at arndb.de> wrote:
> On Wed, Oct 15, 2025, at 12:07, Geert Uytterhoeven wrote:
> > On Tue, 14 Oct 2025 at 18:53, Liam R. Howlett <Liam.Howlett at oracle.com> wrote:
> >> It is odd that this only shows up in certain cases though.  Is there a
> >> particular config option that is needed to cause the size to grow beyond
> >> 1024?
> >
> > And of course there is: I still had a few 64-bit .configs that were
> > derived from older 32-bit .configs, and thus still had
> > CONFIG_FRAME_WARN=1024 :-(
> > Changing them to match the recommended default fixed the issue:
> >
> >     config FRAME_WARN
> >             int "Warn for stack frames larger than"
> >             ...
> >             default 1024 if !64BIT
> >             default 2048 if 64BIT
> >
> > Sorry for the noise...
>
> I have a series that reduces the default warning limit for 64-bit,
> but adds some slack for certain options such as KASAN that
> are known to cause larger stacks throughout.
>
> MIPS does have larger stack usage than most other architectures
> here, and I do account for that with an architecture specific
> base value as well, but in order to catch actual bugs in newly
> written code, this has to be as small as possible.
>
> What is the stack usage you observe in your configuration?

1056 bytes on arm64, 1040 on mips64, i.e. just above the "32-bit"
default of 1024, but far from the "64-bit" default of 2048.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds