[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb3ea155c4e149eca30ca870e3f2546d@AcuMS.aculab.com>
Date: Sun, 7 Aug 2022 17:36:48 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Arnd Bergmann' <arnd@...nel.org>,
Nathan Chancellor <nathan@...nel.org>
CC: Harry Wentland <harry.wentland@....com>,
"Siqueira, Rodrigo" <Rodrigo.Siqueira@....com>,
clang-built-linux <llvm@...ts.linux.dev>,
"David Airlie" <airlied@...ux.ie>,
"Pan, Xinhui" <Xinhui.Pan@....com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
Christian König <christian.koenig@....com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"Alex Deucher" <alexander.deucher@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Sudip Mukherjee (Codethink)" <sudipm.mukherjee@...il.com>
Subject: RE: mainline build failure for x86_64 allmodconfig with clang
From: Arnd Bergmann
> Sent: 05 August 2022 20:32
...
> One thing to try would be to condense a function call like
>
> dml32_CalculateWatermarksMALLUseAndDRAMSpeedChangeSupport(
>
...
> .... /* more arguments */);
>
> into calling conventions that take a pointer to 'mode_lib->vba' and another
> one to 'v', so these are no longer passed on the stack individually.
Or, if it is only called once (I can't find the source)
force it to be inlined.
Or just shoot the software engineer who thinks 100 arguments
is sane. :-)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists