From: Mario Limonciello <superm1@kernel.org>
To: IVAN.LIPSKI@amd.com, amd-gfx@lists.freedesktop.org
Cc: Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>, Alex Hung <alex.hung@amd.com>
Subject: Re: [PATCH] drm/amd/display: Bump frame warning limit for clang builds of dml
Date: Fri, 21 Aug 2026 17:35:05 -0500 [thread overview]
Message-ID: <d30ea1a8-36d1-4d1b-b13c-06e36d7523f0@kernel.org> (raw)
In-Reply-To: <20260821223251.692196-1-IVAN.LIPSKI@amd.com>
On 8/21/26 17:32, IVAN.LIPSKI@amd.com wrote:
> From: Ivan Lipski <ivan.lipski@amd.com>
>
> [Why&How]
> When building the DML files with clang without any sanitizer or LTO,
> the following -Wframe-larger-than errors break the build under
> CONFIG_WERROR:
>
> display_mode_vba_30.c: error: stack frame size (2512) exceeds limit
> (2048) in 'dml30_ModeSupportAndSystemConfigurationFull'
> display_mode_vba_31.c: error: stack frame size (2416) exceeds limit
> (2048) in 'dml31_ModeSupportAndSystemConfigurationFull'
> display_mode_vba_314.c: error: stack frame size (2392) exceeds limit
> (2048) in 'dml314_ModeSupportAndSystemConfigurationFull'
>
> Clang consistently spills more than gcc, pushing the frame past the 2048
> byte limit.
>
> Apply an existing approach of increasing the warn stack size to the
> non-sanitizer path so plain clang builds use a 3072 byte limit.
>
> Closes: https://gitlab.freedesktop.org/drm/amd/-/work_items/5642
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>>
> Signed-off-by: Ivan Lipski <ivan.lipski@amd.com>
> ---
> drivers/gpu/drm/amd/display/dc/dml/Makefile | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/dml/Makefile b/drivers/gpu/drm/amd/display/dc/dml/Makefile
> index 10d4ace04d4f1..99da9dbd62b75 100644
> --- a/drivers/gpu/drm/amd/display/dc/dml/Makefile
> +++ b/drivers/gpu/drm/amd/display/dc/dml/Makefile
> @@ -36,7 +36,11 @@ ifneq ($(CONFIG_FRAME_WARN),0)
> frame_warn_limit := 3072
> endif
> else
> - frame_warn_limit := 2048
> + ifeq ($(CONFIG_CC_IS_CLANG),y)
> + frame_warn_limit := 3072
> + else
> + frame_warn_limit := 2048
> + endif
> endif
>
> ifeq ($(call test-lt, $(CONFIG_FRAME_WARN), $(frame_warn_limit)),y)
prev parent reply other threads:[~2026-08-21 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 22:32 [PATCH] drm/amd/display: Bump frame warning limit for clang builds of dml IVAN.LIPSKI
2026-08-21 22:35 ` Mario Limonciello [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=d30ea1a8-36d1-4d1b-b13c-06e36d7523f0@kernel.org \
--to=superm1@kernel.org \
--cc=IVAN.LIPSKI@amd.com \
--cc=alex.hung@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=sunpeng.li@amd.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