From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: "Pillai, Aurabindo" <Aurabindo.Pillai@amd.com>,
Yujie Liu <yujie.liu@intel.com>
Cc: "Zhuo, Lillian" <Qingqing.Zhuo@amd.com>,
kernel test robot <lkp@intel.com>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
"Li, Roman" <Roman.Li@amd.com>
Subject: Re: drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6193:12: warning: stack frame size (3368) exceeds limit (2048) in 'dml_core_mode_support'
Date: Wed, 17 Apr 2024 13:15:11 +0200 [thread overview]
Message-ID: <186b252f-e37e-4152-b6c7-6fc3754f3b16@intel.com> (raw)
In-Reply-To: <CH0PR12MB5284F7B96B16E8F86E4740CD8B452@CH0PR12MB5284.namprd12.prod.outlook.com>
From: Pillai, Aurabindo <Aurabindo.Pillai@amd.com>
Date: Wed, 7 Feb 2024 16:09:27 +0000
> [AMD Official Use Only - General]
>
>
> Thank you all, I'm able to repro the issue and I have a fix. I'll have
> it run through the internal CI and send it out.
I'm facing it again on the latest -rc4 and Clang 19 (the latest master Git):
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6710:12:
warning: stack frame size (2128) exceeds limit (2048) in
'dml_core_mode_support' [-Wframe-larger-than]
6710 | dml_bool_t dml_core_mode_support(struct display_mode_lib_st
*mode_lib)
| ^
1 warning generated.
Please fix it once and forever somehow, don't abuse the stack =\
Thanks,
Olek
prev parent reply other threads:[~2024-04-17 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 2:01 drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6193:12: warning: stack frame size (3368) exceeds limit (2048) in 'dml_core_mode_support' kernel test robot
2024-02-06 13:20 ` Alexander Lobakin
2024-02-06 16:06 ` Zhuo, Lillian
[not found] ` <CH0PR12MB52845186C7D747A4547DA99A8B462@CH0PR12MB5284.namprd12.prod.outlook.com>
2024-02-07 3:09 ` Yujie Liu
2024-02-07 12:18 ` Alexander Lobakin
[not found] ` <CH0PR12MB5284F7B96B16E8F86E4740CD8B452@CH0PR12MB5284.namprd12.prod.outlook.com>
2024-04-17 11:15 ` Alexander Lobakin [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=186b252f-e37e-4152-b6c7-6fc3754f3b16@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Roman.Li@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yujie.liu@intel.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