From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Fangrui Song <maskray@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
Kees Cook <keescook@chromium.org>,
Justin Stitt <justinstitt@google.com>
Subject: Re: ld.lld: error: unknown argument '--ppc476-workaround'
Date: Fri, 27 Sep 2024 05:25:53 -0700 [thread overview]
Message-ID: <20240927122553.GA908795@thelio-3990X> (raw)
In-Reply-To: <202409251512.QHl7WqZN-lkp@intel.com>
On Wed, Sep 25, 2024 at 03:54:20PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 684a64bf32b6e488004e0ad7f0d7e922798f65b6
> commit: e3a9ee963ad8ba677ca925149812c5932b49af69 kbuild: Fix changing ELF file type for output of gen_btf for big endian
> date: 7 months ago
> config: powerpc-randconfig-002-20240925 (https://download.01.org/0day-ci/archive/20240925/202409251512.QHl7WqZN-lkp@intel.com/config)
> compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 7773243d9916f98ba0ffce0c3a960e4aa9f03e81)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240925/202409251512.QHl7WqZN-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202409251512.QHl7WqZN-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> ld.lld: error: unknown argument '--ppc476-workaround'
I supppose LLD does not have this workaround flag. Perhaps this could be
encoded in Kconfig to avoid this?
diff --git a/arch/powerpc/platforms/44x/Kconfig b/arch/powerpc/platforms/44x/Kconfig
index 35a1f4b9f827..3c6c7c774d89 100644
--- a/arch/powerpc/platforms/44x/Kconfig
+++ b/arch/powerpc/platforms/44x/Kconfig
@@ -301,6 +301,7 @@ config APM821xx
config 476FPE_ERR46
depends on 476FPE
+ depends on $(ld-option,--ppc476-workaround)
bool "Enable linker work around for PPC476FPE errata #46"
help
This option enables a work around for an icache bug on 476
next prev parent reply other threads:[~2024-09-27 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 7:54 kernel test robot
2024-09-27 12:25 ` Nathan Chancellor [this message]
2025-01-11 8:52 kernel test robot
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=20240927122553.GA908795@thelio-3990X \
--to=nathan@kernel.org \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=nicolas@fjasle.eu \
--cc=oe-kbuild-all@lists.linux.dev \
/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®