[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <caea391c-f10a-4979-92c3-75964ed7497a@sirena.org.uk>
Date: Fri, 16 Jun 2023 12:56:00 +0100
From: Mark Brown <broonie@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
Rander Wang <rander.wang@...el.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Péter Ujfalusi
<peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
ALSA Development Mailing List <alsa-devel@...a-project.org>
Subject: Re: sound/soc/soc-pcm.c:2089:5: warning: stack frame size (2064)
exceeds limit (2048) in 'dpcm_be_dai_trigger'
On Fri, Jun 16, 2023 at 12:21:13PM +0200, Pierre-Louis Bossart wrote:
> On 6/15/23 20:34, kernel test robot wrote:
> >>> sound/soc/soc-pcm.c:2089:5: warning: stack frame size (2064) exceeds limit (2048) in 'dpcm_be_dai_trigger' [-Wframe-larger-than]
> > int dpcm_be_dai_trigger(struct snd_soc_pcm_runtime *fe, int stream,
> Not sure what causes this warning to show up, the code hasn't changed in
> 1.2 years, nor what to do about it....
One of the sanitisers is doing things which explodes the stack size. I
wouldn't worry about it, one of the toolchain people will probably get
to it at some point if they didn't already (sometimes these things are
done by tuning the compiler flags).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists