-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-Wframe-larger-than instances in drivers/gpu/drm/amd/display/dc/dml with ARCH=x86-64 #1754
Comments
I would be curious to know if the same configuration without LTO shows the same warnings. Based on the variables to spill ratio, it is possible that LTO does more inlining and blows out the stack. |
Without LTO, I've just noticed these two:
|
This is what I get with Kernel 6.1 and Clang-16 (23e3e107dceb1fd8c1fb81d1229f6aab09a1fce2):
|
With Linux
kernel-config: ThinLTO + KCFI |
This series might address those warnings: https://lore.kernel.org/20230110154325.3350916-1-Rodrigo.Siqueira@amd.com/ |
Thanks for the link. The patch-series applies cleanly on top of Linux 6.2-rc4. |
@nathanchance @rodrigosiqueira A big thank-you pointing me to the link and I did a new build including this patch-set and this fixes the warnings for me. Here and formally (patch-series on top of Linux v6.2-rc4): Tested-by: Sedat Dilek sedat.dilek@gmail.com # LLVM-15.0.3 x86-64 |
I can confirm that the warnings are gone with that patchset and clang version 16.0.0 (60b98979241151f8d6ec8af9ebc4da421f4a0258), using FullLTO and x86-64 on my modified Kernel 6.1.7. Tested-by: Marcus Seyfarth m.seyfarth@gmail.com |
Unfortunately - patchset applied on top of Linux v6.2-rc5+ - with
|
I suspect this series that was just sent out will resolve this issue. |
Also, clang-18 has some improvements around stack usage. Since it's not clear to me from this thread what fixed this where (and I can no longer reproduce w/ clang-18), closing. Please reopen with more info if you can reproduce with clang-18+ (containing https://reviews.llvm.org/rGe698695fbbf62e6676f8907665187f2d2c4d814b) |
@nickdesaulniers I've been carrying the following series with my Kernel that addresses this issue to some degree: https://lists.freedesktop.org/archives/amd-gfx/2023-January/088203.html Will there be a backport of your patch for LLVM/Clang-17 or a point release? As we are still in the RC phase, it might be still possible to land this for the Clang-17 release? |
https://reviews.llvm.org/rGe698695fbbf62e6676f8907665187f2d2c4d814b has already been reverted once. I relanded it without any hint to whatever was the matter with it the first time (possibly nothing; it may have been exposing an older issue that's since been found+fixed). So I'm still holding my breath that it will stick and not get reverted a second time. As such, I consider it too high risk to backport; I'd like it to bake longer to ensure it sticks. |
I see similar warnings as posted in #1752 with my x86-64-build of a 6.0.6 Kernel with some patches (more details and config here):
That was seen with FullLTO, my custom LLVM-Toolchain from my repo and clang version 16.0.0 (c97035c49d941e5b196a938f0393f811d1adbd57).
The text was updated successfully, but these errors were encountered: