[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLUPR12MB0691C309AF20EE1655F0F31DF7090@BLUPR12MB0691.namprd12.prod.outlook.com>
Date: Mon, 7 Dec 2015 16:15:22 +0000
From: "Deucher, Alexander" <Alexander.Deucher@....com>
To: 'Borislav Petkov' <bp@...en8.de>,
"Koenig, Christian" <Christian.Koenig@....com>
CC: lkml <linux-kernel@...r.kernel.org>
Subject: RE: radeon -Wmaybe-uninitialized crap
> -----Original Message-----
> From: Borislav Petkov [mailto:bp@...en8.de]
> Sent: Monday, December 07, 2015 3:56 AM
> To: Deucher, Alexander; Koenig, Christian
> Cc: lkml
> Subject: radeon -Wmaybe-uninitialized crap
>
> Hi guys,
>
> this just started appearing when building -rc4. Got fixes yet? :-)
Odd. Nothing related to these variables has changed in years.
Alex
>
> In file included from drivers/gpu/drm/radeon/radeon_mode.h:37:0,
> from drivers/gpu/drm/radeon/radeon.h:80,
> from drivers/gpu/drm/radeon/r100.c:33:
> drivers/gpu/drm/radeon/r100.c: In function ‘r100_bandwidth_update’:
> include/drm/drm_fixed.h:64:13: warning: ‘crit_point_ff.full’ may be used
> uninitialized in this function [-Wmaybe-uninitialized]
> u64 tmp = ((u64)A.full << 13);
> ^
> drivers/gpu/drm/radeon/r100.c:3153:63: note: ‘crit_point_ff.full’ was
> declared here
> fixed20_12 peak_disp_bw, mem_bw, pix_clk, pix_clk2, temp_ff,
> crit_point_ff;
> ^
> drivers/gpu/drm/radeon/r100.c:3583:42: warning: ‘disp_drain_rate.full’ may
> be used uninitialized in this function [-Wmaybe-uninitialized]
> temp_ff.full = read_return_rate.full - disp_drain_rate.full;
> ^
> --
> Regards/Gruss,
> Boris.
>
> ECO tip #101: Trim your mails when you reply.
Powered by blists - more mailing lists