From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: kernel test robot <lkp@intel.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Alan Maguire <alan.maguire@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
dwarves <dwarves@vger.kernel.org>
Subject: Re: [bpf-next:master 8/9] FAILED: load BTF from .tmp_vmlinux1.BTF.1: No such file or directory
Date: Mon, 29 Dec 2025 11:28:10 -0800 [thread overview]
Message-ID: <5c9130f8-dd8a-41c4-8033-d5661f64c01a@linux.dev> (raw)
In-Reply-To: <202512250932.X7mdviuH-lkp@intel.com>
On 12/24/25 5:01 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
> head: f14cdb1367b947d373215e36cfe9c69768dbafc9
> commit: 522397d05e7d4a7c30b91841492360336b24f833 [8/9] resolve_btfids: Change in-place update with raw binary output
> config: nios2-randconfig-001-20251224 (https://download.01.org/0day-ci/archive/20251225/202512250932.X7mdviuH-lkp@intel.com/config)
> compiler: nios2-linux-gcc (GCC) 11.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251225/202512250932.X7mdviuH-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/202512250932.X7mdviuH-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> Complex, interval and imaginary float types are not supported
> Error while encoding BTF.
Hi Dinh, Alan,
Not sure why this has surfaced only now, but it appears that kernel
build with ARCH=nios2 and CONFIG_DEBUG_INFO_BTF=y has been broken for
a long time.
I tried the following revisions:
- bpf-next @ 522397d05e7d as in bug report
- bpf-next @ 014e1cdb5fad without the gen-btf.sh patch
- v6.18
- v6.17
- v6.12 (~1y ago)
All fail with the same error in pahole [1]:
Complex, interval and imaginary float types are not supported
Encountered error while encoding BTF.
I used v1.24 in most experiments, the default debian:bookworm
installation. Upgrading pahole to v1.31 doesn't change this behavior.
I also stumbled on a phoronix article [2], saying Nios II support has
ended with GCC 15. Is it actively supported in Linux?
Not clear to me if anything needs to be fixed here. I'd appreciate any input.
Thanks.
[1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/btf_encoder.c?h=v1.31#n469
[2] https://www.phoronix.com/news/GCC-15-Drops-Altera-Nios-II
>>> FAILED: load BTF from .tmp_vmlinux1.BTF.1: No such file or directory
>
next parent reply other threads:[~2025-12-29 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202512250932.X7mdviuH-lkp@intel.com>
2025-12-29 19:28 ` Ihor Solodrai [this message]
2026-01-05 16:47 ` [bpf-next:master 8/9] FAILED: load BTF from .tmp_vmlinux1.BTF.1: No such file or directory Alan Maguire
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=5c9130f8-dd8a-41c4-8033-d5661f64c01a@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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