Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [tglx-devel:core/rseq 5/11] kernel/sched/membarrier.c:208:6: error: call to undeclared function 'rseq_v2'; ISO C99 and later do not support implicit function declarations
Date: Thu, 30 Apr 2026 03:30:47 +0800	[thread overview]
Message-ID: <202604300311.aIKKS59R-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git core/rseq
head:   9a2253d7640f6b319562dda1a87cee3416c5d332
commit: a86e32c235afd7ea34ee7ecca5ce532b918930c2 [5/11] rseq: Revert to historical performance killing behaviour
config: um-allnoconfig (https://download.01.org/0day-ci/archive/20260430/202604300311.aIKKS59R-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604300311.aIKKS59R-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/202604300311.aIKKS59R-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from kernel/sched/build_utility.c:97:
>> kernel/sched/membarrier.c:208:6: error: call to undeclared function 'rseq_v2'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     208 |         if (rseq_v2(current))
         |             ^
   1 error generated.


vim +/rseq_v2 +208 kernel/sched/membarrier.c

   191	
   192	static void ipi_rseq(void *info)
   193	{
   194		/*
   195		 * Ensure that all stores done by the calling thread are visible
   196		 * to the current task before the current task resumes.  We could
   197		 * probably optimize this away on most architectures, but by the
   198		 * time we've already sent an IPI, the cost of the extra smp_mb()
   199		 * is negligible.
   200		 */
   201		smp_mb();
   202		/*
   203		 * Legacy mode requires that IDs are written and the critical section is
   204		 * evaluated. V2 optimized mode handles the critical section and IDs are
   205		 * only updated if they change as a consequence of preemption after
   206		 * return from this IPI.
   207		 */
 > 208		if (rseq_v2(current))
   209			rseq_sched_switch_event(current);
   210		else
   211			rseq_force_update();
   212	}
   213	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-04-29 19:31 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=202604300311.aIKKS59R-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@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