Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 22 Jul 2022 12:52:12 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Alex Deucher <alexdeucher@gmail.com>
Cc:     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
Message-ID: <20220722125212.2af3601f@canb.auug.org.au>
In-Reply-To: <20220721121618.049b9c00@canb.auug.org.au>
References: <20220719123607.63cbb3c5@canb.auug.org.au>
        <20220720124732.4aeb3748@canb.auug.org.au>
        <20220721121618.049b9c00@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/NP/Ofe+VdNgQVCiX/k4m2Tu";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/NP/Ofe+VdNgQVCiX/k4m2Tu
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

On Thu, 21 Jul 2022 12:16:18 +1000 Stephen Rothwell <sfr@canb.auug.org.au> =
wrote:
>
> Hi all,
>=20
> On Wed, 20 Jul 2022 12:47:32 +1000 Stephen Rothwell <sfr@canb.auug.org.au=
> wrote:
> >  =20
> > > drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_3=
2.c: In function 'dml32_ModeSupportAndSystemConfigurationFull':
> > > drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_3=
2.c:3799:1: error: the frame size of 2464 bytes is larger than 2048 bytes [=
-Werror=3Dframe-larger-than=3D]
> > >  3799 | } // ModeSupportAndSystemConfigurationFull
> > >       | ^   =20
> >=20
> > This is still here, but the frame size is down to 2336. =20
>=20
> Today it is down to 2128.

And today we are back up to 2152.  I can only imagine that maybe things
are being inlined?

My compiler (in case it matters):

$ x86_64-linux-gnu-gcc --version
x86_64-linux-gnu-gcc (Debian 11.2.0-9) 11.2.0

--=20
Cheers,
Stephen Rothwell

--Sig_/NP/Ofe+VdNgQVCiX/k4m2Tu
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmLaENwACgkQAVBC80lX
0GzfYgf+NvDue/RQTedFHbyjc/uAnLRpQP82QEAm9O11k9o+O2mvx4rSnmh5SDec
uSu+RSS5pw3Jd2O0lmLq/FJUd9uym/Y6tO3YT6x0sWD1h0ZOXpYfLW8rBd+LDTmb
ao87KYl8g8t4T6mSOIhApvsKB2GUei8Uf9+1FosmEfB/CUA+KyiHW49jI/nQ3f2o
HmgE3X3S/dw5btRYik0YfaYefEwmaQ6+TnSpoD+KLwSfhzCuNt8lbUSY/UHO3ty7
2GRKgtsSdgGoigBBQubMZnJ/dPMpTyS1UjsBXrW0GTuiSHnz44PKPKeXHM/NVRAo
pzvUHRA3yYN1JJqyH2BalZCpsN8IYg==
=Ochr
-----END PGP SIGNATURE-----

--Sig_/NP/Ofe+VdNgQVCiX/k4m2Tu--