mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-mips@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Paul Burton <paulburton@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
	<llvm@lists.linux.dev>
Subject: Re: [PATCH] MIPS: Avoid dead code/data elimination when using recordmcount
Date: Thu, 5 Nov 2026 16:23:59 +0100	[thread overview]
Message-ID: <auyfj9MyvQFX-VGf@alpha.franken.de> (raw)
In-Reply-To: <20261004234826.541468-1-rosenp@gmail.com>

On Sun, Oct 04, 2026 at 04:48:26PM -0700, Rosen Penev wrote:
> CONFIG_LD_DEAD_CODE_DATA_ELIMINATION builds with -ffunction-sections,
> placing every function in its own section. recordmcount refuses to use
> weak symbols as section bases, as a strong definition could override
> them, so a weak function alone in its section, such as the generic
> pcibios_fixup_bus() stub, breaks the build:
> 
>   Cannot find symbol for section 88: .text.pcibios_fixup_bus.
>   drivers/pci/probe.o: failed
> 
> MIPS always records mcount locations with recordmcount, so this hits
> any config with the function tracer and dead code elimination enabled,
> e.g. malta_defconfig built with LLVM=1.
> 
> Only offer dead code elimination when recordmcount is not used, as
> powerpc does since commit f8b2336f15f3 ("powerpc: Avoid dead code/data
> elimination when using recordmcount"). In practice this makes it
> unavailable together with the function tracer on MIPS.
> 
> Fixes: c0436b503591 ("MIPS: Enable dead code elimination")
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
>  arch/mips/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index ddabe25d6bf7..f4f82bd75b66 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -79,7 +79,7 @@ config MIPS
>  	select HAVE_IRQ_TIME_ACCOUNTING
>  	select HAVE_KPROBES
>  	select HAVE_KRETPROBES
> -	select HAVE_LD_DEAD_CODE_DATA_ELIMINATION
> +	select HAVE_LD_DEAD_CODE_DATA_ELIMINATION if !FTRACE_MCOUNT_USE_RECORDMCOUNT
>  	select HAVE_MOD_ARCH_SPECIFIC
>  	select HAVE_NMI
>  	select HAVE_PAGE_SIZE_4KB if !CPU_LOONGSON2EF && !CPU_LOONGSON64
> -- 
> 2.56.0

applied to mips-fixes

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-11-05 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 23:48 Rosen Penev
2026-11-05 15:23 ` Thomas Bogendoerfer [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=auyfj9MyvQFX-VGf@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=paulburton@kernel.org \
    --cc=rosenp@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

all inboxes | Powered by JetHome®