All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: clang-built-linux <llvm@lists.linux.dev>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.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
Date: Mon, 14 Apr 2025 09:18:16 -0700	[thread overview]
Message-ID: <20250414161816.GA33918@ax162> (raw)
In-Reply-To: <CA+G9fYvnun+bhYgtt425LWxzOmj+8Jf3ruKeYxQSx-F6U7aisg@mail.gmail.com>

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@linaro.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

      reply	other threads:[~2025-04-14 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 16:07 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 Naresh Kamboju
2025-04-14 16:18 ` Nathan Chancellor [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=20250414161816.GA33918@ax162 \
    --to=nathan@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.