From: Philip Li <philip.li@intel.com>
To: Mukesh Kumar Chaurasiya <mkchauras@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Link Mauve <linkmauve@linkmauve.fr>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Subject: Re: warning: unknown and unstable feature specified for `-Ctarget-feature`: `mma`
Date: Sat, 19 Sep 2026 21:19:41 +0800 [thread overview]
Message-ID: <aq6L7SCSRE2XwB/q@rli9-mobl> (raw)
In-Reply-To: <aqzPCnhvogJ9XEJg@li-1a3e774c-28e4-11b2-a85c-acc9f2883e29.ibm.com>
On Fri, Sep 18, 2026 at 11:12:13AM +0530, Mukesh Kumar Chaurasiya wrote:
> On Thu, Sep 17, 2026 at 03:38:46PM +0200, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 238650ef6c7c7cca08e032527329424c9fbd70e5
> > commit: bc87cbdb952e9223616b839d64bdb4723aa2ed1d powerpc: Enable Rust for ppc64le
> > date: 7 weeks ago
> > config: powerpc64-randconfig-r2201-20260917 (https://download.01.org/0day-ci/archive/20260917/202609171549.xeqQabC6-lkp@intel.com/config)
> > compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> > rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
> > smatch: v0.5.0-9187-g5189e3fb
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260917/202609171549.xeqQabC6-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
> > | Fixes: bc87cbdb952e ("powerpc: Enable Rust for ppc64le")
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202609171549.xeqQabC6-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> warning: unknown and unstable feature specified for `-Ctarget-feature`: `mma`
> > |
> > = note: it is still passed through to the codegen backend, but use of this feature might be unsound and the behavior of this feature can change in the future
> > = help: consider filing a feature request
> > --
> > >> warning: unstable feature specified for `-Ctarget-feature`: `vsx`
> > |
> > = note: this feature is not stably supported; its behavior can change in the future
> > --
> > >> warning: unknown and unstable feature specified for `-Ctarget-feature`: `hard-float`
> > |
> > = note: it is still passed through to the codegen backend, but use of this feature might be unsound and the behavior of this feature can change in the future
> > = help: consider filing a feature request
> > --
> > >> warning: unstable feature specified for `-Ctarget-feature`: `altivec`
> > |
> > = note: this feature is not stably supported; its behavior can change in the future
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
> This is expected, the issue for the same is raised to rust-lang.
Thanks for the info, I will configure the bot to avoid reporting this again.
>
> Regards,
> Mukesh
>
prev parent reply other threads:[~2026-09-19 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:38 kernel test robot
2026-09-18 5:42 ` Mukesh Kumar Chaurasiya
2026-09-19 13:19 ` 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=aq6L7SCSRE2XwB/q@rli9-mobl \
--to=philip.li@intel.com \
--cc=chleroy@kernel.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maddy@linux.ibm.com \
--cc=mkchauras@gmail.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®