From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 7/7 v4] sh: mcount.S: fix build error when PRINTK is not enabled
Date: Mon, 20 Mar 2023 10:13:30 +0100 [thread overview]
Message-ID: <01f84314b2499b6859a4826ecf7363635e66a4fc.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdU+tsKuONm9iPqqTFSnRT2zaV3zogYgc-+vCp6x-ruQ_w@mail.gmail.com>
Hi Geert!
On Mon, 2023-03-20 at 09:16 +0100, Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Sun, Mar 19, 2023 at 9:49 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > On Sun, 2023-03-05 at 20:00 -0800, Randy Dunlap wrote:
> > > Fix a build error in mcount.S when CONFIG_PRINTK is not enabled.
> > > Fixes this build error:
> > >
> > > sh2-linux-ld: arch/sh/lib/mcount.o: in function `stack_panic':
> > > (.text+0xec): undefined reference to `dump_stack'
> > >
> > > Fixes: e460ab27b6c3 ("sh: Fix up stack overflow check with ftrace disabled.")
> > > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > > Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> > > Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> > > Cc: Rich Felker <dalias@libc.org>
> > > Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > > Cc: stable@vger.kernel.org
> > > ---
> > > v2: add PRINTK to STACK_DEBUG dependency (thanks, Geert)
> > > v3: skipped
> > > v4: refresh & resend
> > >
> > > arch/sh/Kconfig.debug | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff -- a/arch/sh/Kconfig.debug b/arch/sh/Kconfig.debug
> > > --- a/arch/sh/Kconfig.debug
> > > +++ b/arch/sh/Kconfig.debug
> > > @@ -15,7 +15,7 @@ config SH_STANDARD_BIOS
> > >
> > > config STACK_DEBUG
> > > bool "Check for stack overflows"
> > > - depends on DEBUG_KERNEL
> > > + depends on DEBUG_KERNEL && PRINTK
> > > help
> > > This option will cause messages to be printed if free stack space
> > > drops below a certain limit. Saying Y here will add overhead to
> >
> > I can't really test this change as the moment I am enabling CONFIG_STACK_DEBUG,
> > the build fails with:
> >
> > CC scripts/mod/devicetable-offsets.s
> > sh4-linux-gcc: error: -pg and -fomit-frame-pointer are incompatible
> > make[1]: *** [scripts/Makefile.build:252: scripts/mod/empty.o] Error 1
> > make[1]: *** Waiting for unfinished jobs....
> > sh4-linux-gcc: error: -pg and -fomit-frame-pointer are incompatible
> > make[1]: *** [scripts/Makefile.build:114: scripts/mod/devicetable-offsets.s] Error 1
> > make: *** [Makefile:1286: prepare0] Error 2
> >
> > So, I assume we need to strip -fomit-frame-pointer from KBUILD_CFLAGS, correct?
> >
> > I tried this change, but that doesn't fix it for me:
> >
> > diff --git a/arch/sh/Makefile b/arch/sh/Makefile
> > index 5c8776482530..83f535b73835 100644
> > --- a/arch/sh/Makefile
> > +++ b/arch/sh/Makefile
> > @@ -173,6 +173,7 @@ KBUILD_AFLAGS += $(cflags-y)
> >
> > ifeq ($(CONFIG_MCOUNT),y)
> > KBUILD_CFLAGS += -pg
> > + KBUILD_CFLAGS := $(subst -fomit-frame-pointer,,$(KBUILD_CFLAGS))
> > endif
> >
> > ifeq ($(CONFIG_DWARF_UNWINDER),y)
> >
> > Any ideas?
>
> Please try with "+=" instead of ":=".
That doesn't work either. I tried the following, but that didn't strip -fomit-frame-pointer:
diff --git a/arch/sh/Makefile b/arch/sh/Makefile
index 5c8776482530..9eef6f6ffc8b 100644
--- a/arch/sh/Makefile
+++ b/arch/sh/Makefile
@@ -172,7 +172,7 @@ KBUILD_CPPFLAGS += $(cflags-y)
KBUILD_AFLAGS += $(cflags-y)
ifeq ($(CONFIG_MCOUNT),y)
- KBUILD_CFLAGS += -pg
+ KBUILD_CFLAGS := $(subst -fomit-frame-pointer,,$(KBUILD_CFLAGS)) -pg
endif
ifeq ($(CONFIG_DWARF_UNWINDER),y)
I will have to do some more digging tonight.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-03-20 9:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 4:00 [PATCH 0/7 v4] sh: various doc, build, init fixes Randy Dunlap
2023-03-06 4:00 ` [PATCH 1/7 v4] sh: SH2007: drop the bad URL info Randy Dunlap
2023-03-19 19:22 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 2/7 v4] sh: nmi_debug: fix return value of __setup handler Randy Dunlap
2023-03-19 19:32 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 3/7 v4] sh: init: use OF_EARLY_FLATTREE for early init Randy Dunlap
2023-03-19 19:48 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 4/7 v4] sh: math-emu: fix macro redefined warning Randy Dunlap
2023-03-19 19:49 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments Randy Dunlap
2023-03-16 13:23 ` John Paul Adrian Glaubitz
2023-03-16 16:44 ` Randy Dunlap
2023-03-16 16:52 ` John Paul Adrian Glaubitz
2023-03-16 20:43 ` Randy Dunlap
2023-03-16 20:46 ` John Paul Adrian Glaubitz
2023-03-17 7:31 ` Geert Uytterhoeven
2023-03-17 7:51 ` John Paul Adrian Glaubitz
2023-03-19 19:50 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 6/7 v4] sh: fix Kconfig entry for NUMA => SMP Randy Dunlap
2023-03-19 20:20 ` John Paul Adrian Glaubitz
2023-03-20 20:13 ` John Paul Adrian Glaubitz
2023-03-20 20:17 ` Randy Dunlap
2023-03-06 4:00 ` [PATCH 7/7 v4] sh: mcount.S: fix build error when PRINTK is not enabled Randy Dunlap
2023-03-19 20:49 ` John Paul Adrian Glaubitz
2023-03-20 8:16 ` Geert Uytterhoeven
2023-03-20 9:13 ` John Paul Adrian Glaubitz [this message]
2023-03-20 12:42 ` Geert Uytterhoeven
2023-03-20 12:43 ` Geert Uytterhoeven
2023-03-20 13:32 ` John Paul Adrian Glaubitz
2023-03-20 20:10 ` John Paul Adrian Glaubitz
2023-03-20 20:09 ` John Paul Adrian Glaubitz
2023-03-07 15:18 ` [PATCH 0/7 v4] sh: various doc, build, init fixes John Paul Adrian Glaubitz
2023-03-16 13:26 ` John Paul Adrian Glaubitz
2023-03-23 9:41 ` John Paul Adrian Glaubitz
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=01f84314b2499b6859a4826ecf7363635e66a4fc.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stable@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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®