From: kernel test robot <lkp@intel.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg+lists@ziepe.ca>,
linux-rdma@vger.kernel.org
Subject: [rdma:wip/leon-for-next] BUILD REGRESSION c9085ec66448094d7863a80c4633954bdd1f1e4e
Date: Fri, 14 Aug 2026 09:36:37 +0800 [thread overview]
Message-ID: <202608140923.gmPYKSVT-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git wip/leon-for-next
branch HEAD: c9085ec66448094d7863a80c4633954bdd1f1e4e RDMA/ucma: Allow path records to exactly fit the output buffer
Unverified Error/Warning (likely false positive, kindly check if interested):
drivers/infiniband/hw/cxgb4/mem.c:584:1: internal compiler error: in final_scan_insn_1, at final.cc:2823
drivers/infiniband/hw/mthca/mthca_provider.c:946:1: internal compiler error: in final_scan_insn_1, at final.cc:2823
Error/Warning ids grouped by kconfigs:
recent_errors
`-- csky-allmodconfig
|-- drivers-infiniband-hw-cxgb4-mem.c:internal-compiler-error:in-final_scan_insn_1-at-final.cc
`-- drivers-infiniband-hw-mthca-mthca_provider.c:internal-compiler-error:in-final_scan_insn_1-at-final.cc
elapsed time: 769m
configs tested: 15
configs skipped: 0
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
csky allmodconfig gcc-16.1.0
i386 allmodconfig gcc-14
loongarch defconfig clang-24
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc defconfig gcc-16.1.0
sh ap325rxa_defconfig gcc-16.1.0
sh defconfig gcc-16.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 1:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608140923.gmPYKSVT-lkp@intel.com \
--to=lkp@intel.com \
--cc=dledford@redhat.com \
--cc=jgg+lists@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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