Re: [PATCH] ARM: require GCC for FRAME_POINTER

2018-08-13 Thread Arnd Bergmann
On Sat, Aug 11, 2018 at 11:52 AM Stefan Agner wrote: > > diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug > index 693f84392f1b..cb65cf67dfa2 100644 > --- a/arch/arm/Kconfig.debug > +++ b/arch/arm/Kconfig.debug > @@ -54,7 +54,7 @@ config DEBUG_WX > # n, but then RMK will have to kill

Re: [PATCH] ARM: require GCC for FRAME_POINTER

2018-08-13 Thread Arnd Bergmann
On Sat, Aug 11, 2018 at 11:52 AM Stefan Agner wrote: > > diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug > index 693f84392f1b..cb65cf67dfa2 100644 > --- a/arch/arm/Kconfig.debug > +++ b/arch/arm/Kconfig.debug > @@ -54,7 +54,7 @@ config DEBUG_WX > # n, but then RMK will have to kill

[PATCH] ARM: require GCC for FRAME_POINTER

2018-08-11 Thread Stefan Agner
To produce a meaningful backtrace with FRAME_POINTER enabled the kernel needs a specific function prologue: movip, sp stmfdsp!, {fp, ip, lr, pc} subfp, ip, #4 To get to the required prologue gcc uses apcs and no-sched-prolog. This compiler options are not available on

[PATCH] ARM: require GCC for FRAME_POINTER

2018-08-11 Thread Stefan Agner
To produce a meaningful backtrace with FRAME_POINTER enabled the kernel needs a specific function prologue: movip, sp stmfdsp!, {fp, ip, lr, pc} subfp, ip, #4 To get to the required prologue gcc uses apcs and no-sched-prolog. This compiler options are not available on