From: kernel test robot <lkp@intel.com>
To: Nick Terrell <terrelln@fb.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: lib/zstd/compress/zstd_opt.c:1324:15: warning: stack frame size (2384) exceeds limit (2048) in 'ZSTD_compressBlock_opt0'
Date: Sun, 23 Jul 2023 20:30:50 +0800 [thread overview]
Message-ID: <202307232022.GrGHbMYi-lkp@intel.com> (raw)
Hi Nick,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c2782531397f5cb19ca3f8f9c17727f1cdf5bee8
commit: 2aa14b1ab2c41a4fe41efae80d58bb77da91f19f zstd: import usptream v1.5.2
date: 9 months ago
config: riscv-randconfig-r032-20230723 (https://download.01.org/0day-ci/archive/20230723/202307232022.GrGHbMYi-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230723/202307232022.GrGHbMYi-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/202307232022.GrGHbMYi-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/zstd/compress/zstd_opt.c:1324:15: warning: stack frame size (2384) exceeds limit (2048) in 'ZSTD_compressBlock_opt0' [-Wframe-larger-than]
static size_t ZSTD_compressBlock_opt0(
^
>> lib/zstd/compress/zstd_opt.c:1331:15: warning: stack frame size (2320) exceeds limit (2048) in 'ZSTD_compressBlock_opt2' [-Wframe-larger-than]
static size_t ZSTD_compressBlock_opt2(
^
2 warnings generated.
vim +/ZSTD_compressBlock_opt0 +1324 lib/zstd/compress/zstd_opt.c
1323
> 1324 static size_t ZSTD_compressBlock_opt0(
1325 ZSTD_matchState_t* ms, seqStore_t* seqStore, U32 rep[ZSTD_REP_NUM],
1326 const void* src, size_t srcSize, const ZSTD_dictMode_e dictMode)
1327 {
1328 return ZSTD_compressBlock_opt_generic(ms, seqStore, rep, src, srcSize, 0 /* optLevel */, dictMode);
1329 }
1330
> 1331 static size_t ZSTD_compressBlock_opt2(
1332 ZSTD_matchState_t* ms, seqStore_t* seqStore, U32 rep[ZSTD_REP_NUM],
1333 const void* src, size_t srcSize, const ZSTD_dictMode_e dictMode)
1334 {
1335 return ZSTD_compressBlock_opt_generic(ms, seqStore, rep, src, srcSize, 2 /* optLevel */, dictMode);
1336 }
1337
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-23 12:31 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=202307232022.GrGHbMYi-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=terrelln@fb.com \
/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