[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250414161816.GA33918@ax162>
Date: Mon, 14 Apr 2025 09:18:16 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: clang-built-linux <llvm@...ts.linux.dev>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>,
open list <linux-kernel@...r.kernel.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: x86_64 clang-20 clang-nightly config lto-full failed - ld.lld:
error: linking module flags 'Code Model': IDs have conflicting values: 'i32
1' from vmlinux.a(gdt_idt.o at 1321040), and 'i32 2' from ld-temp.o
Hi Naresh,
On Mon, Apr 14, 2025 at 09:37:51PM +0530, Naresh Kamboju wrote:
> Regressions on x86_64 config LTO_CLANG_FULL with korg-clang-20 and
> clang-nightly on the
> Linux next-20250407 and found again on next-20250414 tag
>
> First seen on the next-20250407.
> Bad: next-20250407 and next-20250414
> Good:next-20250404
>
> * x86_64, Build
> - Build/korg-clang-20-lkftconfig-lto-full
> - Build/clang-nightly-lkftconfig-lto-full
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
>
> Build regression: x86_64 clang-20 clang-nightly config lto-full failed
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> ## Build log
> ld.lld: error: linking module flags 'Code Model': IDs have conflicting
> values: 'i32 1'
> from vmlinux.a(gdt_idt.o at 1321040), and 'i32 2' from ld-temp.o
Thanks for the report, I will be sending a patch to fix this today.
Cheers,
Nathan
Powered by blists - more mailing lists