From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jolsa-perf:bpf/optimized_uprobe_6 1/2] <inline asm>:8:6: error: unexpected token in operand
Date: Mon, 11 Mar 2024 03:10:57 +0800 [thread overview]
Message-ID: <202403110341.2BY3e9dL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/optimized_uprobe_6
head: 89ec186aa763b7de4f2846f57d5f7ffc38d72077
commit: c46975c90ceef8ec72cfa1826b02ebea142c1787 [1/2] uprobe: Add syscall to speed up return probe
config: arm-defconfig (https://download.01.org/0day-ci/archive/20240311/202403110341.2BY3e9dL-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240311/202403110341.2BY3e9dL-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/202403110341.2BY3e9dL-lkp@intel.com/
All errors (new ones prefixed by >>):
>> <inline asm>:8:6: error: unexpected token in operand
push %rax
^
>> <inline asm>:9:11: error: unknown token in expression
mov $462, %rax
^
>> <inline asm>:9:11: error: malformed expression
mov $462, %rax
^
>> <inline asm>:10:1: error: invalid instruction
syscall
^
4 errors generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-10 19:11 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=202403110341.2BY3e9dL-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--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 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.