mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: {standard input}:384: Error: Invalid operands
Date: Fri, 27 Mar 2026 12:35:30 +0800	[thread overview]
Message-ID: <acYJEonqWHNtv1nG@rli9-mobl> (raw)
In-Reply-To: <202603270555.zPdpChGv-lkp@intel.com>

On Fri, Mar 27, 2026 at 05:31:18AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   d813f421930c5b01b9f61043932de02602dd6ae3
> commit: a46023d5616ed3ed781e56ca93400eb9490e3646 tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast
> date:   8 weeks ago
> config: parisc-defconfig (https://download.01.org/0day-ci/archive/20260327/202603270555.zPdpChGv-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603270555.zPdpChGv-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/202603270555.zPdpChGv-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):

Kindly ignore this report, it looks like a gcc bug, we will further check
and avoid reporting this again.

> 
>    during RTL pass: final
>    fs/smb/client/netmisc.c: In function 'map_smb_to_linux_error':
>    fs/smb/client/netmisc.c:893:1: internal compiler error: output_operand: operand number missing after %-letter
>      893 | }
>          | ^
>    0x7fdfba8c1d64 __libc_start_main
>    	???:0
>    Please submit a full bug report, with preprocessed source (by using -freport-bug).
>    Please include the complete backtrace with any bug report.
>    See <https://gcc.gnu.org/bugs/> for instructions.
>    {standard input}: Assembler messages:
>    {standard input}:383: Warning: end of file not at end of a line; newline inserted
> >> {standard input}:384: Error: Invalid operands 
> --
>    during RTL pass: final
>    netmisc.c: In function 'map_smb_to_linux_error':
>    netmisc.c:893:1: internal compiler error: output_operand: operand number missing after %-letter
>      893 | }
>          | ^
>    0x7f0298cd2d64 __libc_start_main
>    	???:0
>    Please submit a full bug report, with preprocessed source (by using -freport-bug).
>    Please include the complete backtrace with any bug report.
>    See <https://gcc.gnu.org/bugs/> for instructions.
>    {standard input}: Assembler messages:
>    {standard input}:383: Warning: end of file not at end of a line; newline inserted
> >> {standard input}:384: Error: Invalid operands 
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2026-03-27  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 21:31 kernel test robot
2026-03-27  4:35 ` Philip Li [this message]

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=acYJEonqWHNtv1nG@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®