summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Lipski <ivan.lipski@amd.com>2026-08-21 00:04:53 -0400
committerAlex Deucher <alexander.deucher@amd.com>2026-09-23 15:18:48 -0400
commit21711b6e66bb7b41b1aec67b2d99aafe768c8fcb (patch)
tree9ec5052dc2c06508229b3f4877cfff6ddcbb465f
parentebf8b0fd8508b744f85a8eee82b745b1d3502dd0 (diff)
downloadlinux-21711b6e66bb7b41b1aec67b2d99aafe768c8fcb.tar.gz
linux-21711b6e66bb7b41b1aec67b2d99aafe768c8fcb.zip
drm/amd/display: Bump frame warning limit for clang builds of dml
[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 Signed-off-by: Ivan Lipski <ivan.lipski@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
-rw-r--r--drivers/gpu/drm/amd/display/dc/dml/Makefile6
1 files changed, 5 insertions, 1 deletions
diff --git a/drivers/gpu/drm/amd/display/dc/dml/Makefile b/drivers/gpu/drm/amd/display/dc/dml/Makefile
index 096520bd27c6..79eeb3721b99 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)