From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android-4.14-stable 21099/29940] arm-linux-gnueabi-gcc: error: unrecognized command line option '-ftrivial-auto-var-init=pattern'
Date: Fri, 30 Jun 2023 21:46:55 +0800 [thread overview]
Message-ID: <202306302111.7mpfdTdP-lkp@intel.com> (raw)
Hi glider,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android-4.14-stable
head: e8c1340cbb0f24693dd9056f8d5a7808e4597b80
commit: a7eda6eddca559c1c3a897a35692f9d49d46c9dd [21099/29940] BACKPORT: security: allow using Clang's zero initialization for stack variables
config: arm-randconfig-r046-20230629 (https://download.01.org/0day-ci/archive/20230630/202306302111.7mpfdTdP-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce: (https://download.01.org/0day-ci/archive/20230630/202306302111.7mpfdTdP-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/202306302111.7mpfdTdP-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arm-linux-gnueabi-gcc: error: unrecognized command line option '-ftrivial-auto-var-init=pattern'
make[2]: *** [./Kbuild:22: kernel/bounds.s] Error 1 shuffle=2767728755
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1214: prepare0] Error 2 shuffle=2767728755
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:146: sub-make] Error 2 shuffle=2767728755
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-30 13:47 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=202306302111.7mpfdTdP-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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 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.