From: kernel test robot <lkp@intel.com>
To: Petteri Aimonen <jpa@git.mail.kapsi.fi>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@suse.de>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: /usr/lib/gcc-cross/riscv64-linux-gnu/14/../../../../riscv64-linux-gnu/bin/ld: test_fpu.c:(.text+0x13e): warning: fegetexcept is not implemented and will always fail
Date: Sun, 15 Feb 2026 20:18:35 +0100 [thread overview]
Message-ID: <202602152019.qSJKlF3m-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: bb7a3fc2c976b5d0deb35a54ca237519816d7ba9
commit: 4185b3b92792eaec5869266e594338343421ffb0 selftests/fpu: Add an FPU selftest
date: 6 years ago
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260215/202602152019.qSJKlF3m-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260215/202602152019.qSJKlF3m-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/202602152019.qSJKlF3m-lkp@intel.com/
All warnings (new ones prefixed by >>):
/usr/lib/gcc-cross/riscv64-linux-gnu/14/../../../../riscv64-linux-gnu/bin/ld: /tmp/ccRZDtSR.o: in function `main':
test_fpu.c:(.text+0x106): warning: feenableexcept is not implemented and will always fail
>> /usr/lib/gcc-cross/riscv64-linux-gnu/14/../../../../riscv64-linux-gnu/bin/ld: test_fpu.c:(.text+0x13e): warning: fegetexcept is not implemented and will always fail
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-15 19:19 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=202602152019.qSJKlF3m-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=jpa@git.mail.kapsi.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®