public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org,
	Adrian Ratiu <adrian.ratiu@collabora.com>,
	Ezequiel Garcia <ezequiel@collabora.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: drivers/staging/media/hantro/hantro_g2_hevc_dec.c:536:5: warning: stack frame size (1248) exceeds limit (1024) in function 'hantro_g2_hevc_dec_run'
Date: Thu, 22 Jul 2021 21:46:10 +0800	[thread overview]
Message-ID: <202107222105.fOZEbvak-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

Hi Benjamin,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   3d5895cd351757f69c9a66fb5fc8cf19f454d773
commit: cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c media: hantro: Introduce G2/HEVC decoder
date:   6 weeks ago
config: powerpc64-randconfig-r013-20210722 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 9625ca5b602616b2f5584e8a49ba93c52c141e40)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install powerpc64 cross compiling tool for clang build
        # apt-get install binutils-powerpc64-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout cb5dd5a0fa518dff14ff2b90837c3c8f98f4dd5c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   In file included from drivers/staging/media/hantro/hantro_g2_hevc_dec.c:8:
   In file included from drivers/staging/media/hantro/hantro_hw.h:12:
   In file included from include/linux/interrupt.h:6:
   In file included from include/linux/kernel.h:12:
   In file included from include/linux/bitops.h:32:
   In file included from arch/powerpc/include/asm/bitops.h:62:
   arch/powerpc/include/asm/barrier.h:49:9: warning: '__lwsync' macro redefined [-Wmacro-redefined]
   #define __lwsync()      __asm__ __volatile__ (stringify_in_c(LWSYNC) : : :"memory")
           ^
   <built-in>:310:9: note: previous definition is here
   #define __lwsync __builtin_ppc_lwsync
           ^
>> drivers/staging/media/hantro/hantro_g2_hevc_dec.c:536:5: warning: stack frame size (1248) exceeds limit (1024) in function 'hantro_g2_hevc_dec_run' [-Wframe-larger-than]
   int hantro_g2_hevc_dec_run(struct hantro_ctx *ctx)
       ^
   2 warnings generated.


vim +/hantro_g2_hevc_dec_run +536 drivers/staging/media/hantro/hantro_g2_hevc_dec.c

   535	
 > 536	int hantro_g2_hevc_dec_run(struct hantro_ctx *ctx)

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 42962 bytes --]

             reply	other threads:[~2021-07-22 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 13:46 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-10 21:35 drivers/staging/media/hantro/hantro_g2_hevc_dec.c:536:5: warning: stack frame size (1248) exceeds limit (1024) in function 'hantro_g2_hevc_dec_run' kernel test robot

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=202107222105.fOZEbvak-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.ratiu@collabora.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.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