From: Will Deacon <will@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
llvm@lists.linux.dev, Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org,
Anders Roxell <anders.roxell@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Improve HAVE_DYNAMIC_FTRACE_WITH_REGS selection for clang
Date: Thu, 14 Apr 2022 11:30:52 +0100 [thread overview]
Message-ID: <164992995404.58572.4358662722112998061.b4-ty@kernel.org> (raw)
In-Reply-To: <20220413181420.3522187-1-nathan@kernel.org>
On Wed, 13 Apr 2022 11:14:21 -0700, Nathan Chancellor wrote:
> Will and Anders reported that using just 'CC=clang' with CONFIG_FTRACE=y
> and CONFIG_STACK_TRACER=y would result in an error while linking:
>
> aarch64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.meminit.data' in mm/sparse.o] sections
> aarch64-linux-gnu-ld: final link failed: bad value
>
> This error was exposed by commit f12b034afeb3 ("scripts/Makefile.clang:
> default to LLVM_IAS=1") in combination with binutils older than 2.36.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: Improve HAVE_DYNAMIC_FTRACE_WITH_REGS selection for clang
https://git.kernel.org/arm64/c/45bd8951806e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-04-14 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 18:14 [PATCH] arm64: Improve HAVE_DYNAMIC_FTRACE_WITH_REGS selection for clang Nathan Chancellor
2022-04-14 10:30 ` Will Deacon [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=164992995404.58572.4358662722112998061.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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