Re: linux-next: build failure after merge of the amdgpu tree

From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rodrigo Siqueira Jordao <Rodrigo.Siqueira@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	"Wentland, Harry" <Harry.Wentland@amd.com>,
	"Lei, Jun" <jun.lei@amd.com>,
	"Dhere, Chaitanya" <Chaitanya.Dhere@amd.com>,
	"Zhuo, Qingqing" <qingqing.zhuo@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Roman Li <roman.li@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
Date: Mon, 16 Oct 2023 11:39:46 +1100	[thread overview]
Message-ID: <20231016113946.698ac2da@canb.auug.org.au> (raw)
In-Reply-To: <cc75c480-5359-465e-adab-46b418ec5d97@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

Hi Rodrigo,

On Tue, 10 Oct 2023 15:14:46 -0600 Rodrigo Siqueira Jordao <Rodrigo.Siqueira@amd.com> wrote:
>
> I think I have a fix for that, but some things are unclear to me. I'm
> only able to see this issue when using allmodconfig. Additionally,
> when I inspected the function, it had a few local variables, not
> enough to explode the stack size fwiu. Is there any option in the
> allmodconfig that makes it easy to see this issue? Maybe something
> that I'm missing in my custom config file? Is it possible that
> allmodconfig enables some option that might increase the stack size?
> Perhaps the FPU flags from GCC include something else in the stack?
> 
> Also, for investigating this issue, I'm considering the local
> variables, but as you can see from dml_core_mode_support, it has a
> few pointers. Am I missing something?

This could possibly be caused by inlining of other functions that are
static within the same file.

Other than that, I am also at a loss.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]