From: kernel test robot <lkp@intel.com>
To: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_trace_acpi_support_v1 60/87] arch/riscv/kernel/process.c:207:2: error: call to undeclared function 'flush_ptrace_hw_breakpoint'; ISO C99 and later do not support implicit function declarations
Date: Fri, 02 Oct 2026 06:17:19 +0200 [thread overview]
Message-ID: <202610020620.pgRcphRg-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_trace_acpi_support_v1
head: dc5b9586f90cc15314085bdaa74661fc00d1688f
commit: 2aa069bfc965618a567482f16f10c8098c358d01 [60/87] riscv: ptrace support for hardware break/watchpoints
config: riscv-randconfig-2001-20261002 (https://download.01.org/0day-ci/archive/20261002/202610020620.pgRcphRg-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261002/202610020620.pgRcphRg-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/202610020620.pgRcphRg-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kernel/process.c:207:2: error: call to undeclared function 'flush_ptrace_hw_breakpoint'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
207 | flush_ptrace_hw_breakpoint(current);
| ^
1 error generated.
vim +/flush_ptrace_hw_breakpoint +207 arch/riscv/kernel/process.c
183
184 void flush_thread(void)
185 {
186 #ifdef CONFIG_FPU
187 /*
188 * Reset FPU state and context
189 * frm: round to nearest, ties to even (IEEE default)
190 * fflags: accrued exceptions cleared
191 */
192 fstate_off(current, task_pt_regs(current));
193 memset(¤t->thread.fstate, 0, sizeof(current->thread.fstate));
194 #endif
195 #ifdef CONFIG_RISCV_ISA_V
196 /* Reset vector state */
197 riscv_v_vstate_ctrl_init(current);
198 riscv_v_vstate_off(task_pt_regs(current));
199 kfree(current->thread.vstate.datap);
200 memset(¤t->thread.vstate, 0, sizeof(struct __riscv_v_ext_state));
201 clear_tsk_thread_flag(current, TIF_RISCV_V_DEFER_RESTORE);
202 #endif
203 #ifdef CONFIG_RISCV_ISA_SUPM
204 if (riscv_has_extension_unlikely(RISCV_ISA_EXT_SUPM))
205 envcfg_update_bits(current, ENVCFG_PMM, ENVCFG_PMM_PMLEN_0);
206 #endif
> 207 flush_ptrace_hw_breakpoint(current);
208 }
209
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-02 4:17 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=202610020620.pgRcphRg-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=himanshu.chauhan@oss.qualcomm.com \
--cc=llvm@lists.linux.dev \
--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