[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5cc4fdb6-9a4c-4937-9878-7fcd3d3f0a05@w6rz.net>
Date: Thu, 10 Jul 2025 05:25:43 -0700
From: Ron Economos <re@...z.net>
To: Alexandre Ghiti <alexghiti@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
<palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alex@...ti.fr>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: Stop considering R_RISCV_NONE as bad relocations
On 7/10/25 01:34, Alexandre Ghiti wrote:
> Even though those relocations should not be present in the final
> vmlinux, there are a lot of them. And since those relocations are
> considered "bad", they flood the compilation output which may hide some
> legitimate bad relocations.
>
> Signed-off-by: Alexandre Ghiti <alexghiti@...osinc.com>
> ---
> arch/riscv/tools/relocs_check.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/riscv/tools/relocs_check.sh b/arch/riscv/tools/relocs_check.sh
> index baeb2e7b2290558d696afbc5429d6a3c69ae49e1..742993e6a8cba72c657dd2f8f5dabc4c415e84bd 100755
> --- a/arch/riscv/tools/relocs_check.sh
> +++ b/arch/riscv/tools/relocs_check.sh
> @@ -14,7 +14,9 @@ bad_relocs=$(
> ${srctree}/scripts/relocs_check.sh "$@" |
> # These relocations are okay
> # R_RISCV_RELATIVE
> - grep -F -w -v 'R_RISCV_RELATIVE'
> + # R_RISCV_NONE
> + grep -F -w -v 'R_RISCV_RELATIVE
> +R_RISCV_NONE'
> )
>
> if [ -z "$bad_relocs" ]; then
>
> ---
> base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
> change-id: 20250710-dev-alex-riscv_none_bad_relocs_v1-ba6048681836
>
> Best regards,
Works good.
Tested-by: Ron Economos <re@...z.net>
Powered by blists - more mailing lists