summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
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:53:05 -0400
commit18779dd84515db093fedb4ebaf0998c9b165a5fb (patch)
treec028faac9bdb0993812996278349d5982e779549 /tools/perf/scripts/python/stackcollapse.py
parent0fd5e9ddf362b1253b3c94b858371f90400e5c4a (diff)
downloadlinux-next-18779dd84515db093fedb4ebaf0998c9b165a5fb.tar.gz
linux-next-18779dd84515db093fedb4ebaf0998c9b165a5fb.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> (cherry picked from commit 21711b6e66bb7b41b1aec67b2d99aafe768c8fcb) Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions