From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-next 21/21] hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3ffc0): cannot reach 0000292c_memcpy+0, recompile with -ffunction-sections
Date: Sat, 04 Jul 2026 11:25:13 +0800 [thread overview]
Message-ID: <202607041146.h3kuMa0T-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-next
head: 666d1350fc32c85fe18b1d7be662df141b4f9566
commit: 666d1350fc32c85fe18b1d7be662df141b4f9566 [21/21] netfs: Combine prepare and issue ops and grab the buffers on request
config: parisc-randconfig-r111-20260704 (https://download.01.org/0day-ci/archive/20260704/202607041146.h3kuMa0T-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 10.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607041146.h3kuMa0T-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/202607041146.h3kuMa0T-lkp@intel.com/
All errors (new ones prefixed by >>):
>> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3ffc0): cannot reach 0000292c_memcpy+0, recompile with -ffunction-sections
>> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3ffc0): cannot handle R_PARISC_PCREL17F for memcpy
hppa-linux-ld: final link failed: bad value
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-04 3:25 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=202607041146.h3kuMa0T-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.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 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.