Re: radeon -Wmaybe-uninitialized crap

2015-12-11 Thread Borislav Petkov
On Mon, Dec 07, 2015 at 06:10:02PM +0100, Borislav Petkov wrote: > On Mon, Dec 07, 2015 at 04:15:22PM +, Deucher, Alexander wrote: > > Odd. Nothing related to these variables has changed in years. > > Odd indeed. Building that same config on two other boxes doesn't trip > those up so it must

Re: radeon -Wmaybe-uninitialized crap

2015-12-11 Thread Borislav Petkov
On Mon, Dec 07, 2015 at 06:10:02PM +0100, Borislav Petkov wrote: > On Mon, Dec 07, 2015 at 04:15:22PM +, Deucher, Alexander wrote: > > Odd. Nothing related to these variables has changed in years. > > Odd indeed. Building that same config on two other boxes doesn't trip > those up so it must

Re: radeon -Wmaybe-uninitialized crap

2015-12-07 Thread Borislav Petkov
On Mon, Dec 07, 2015 at 04:15:22PM +, Deucher, Alexander wrote: > Odd. Nothing related to these variables has changed in years. Odd indeed. Building that same config on two other boxes doesn't trip those up so it must be something gcc-related on that particular box. Hmmm. --

RE: radeon -Wmaybe-uninitialized crap

2015-12-07 Thread Deucher, Alexander
> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.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

RE: radeon -Wmaybe-uninitialized crap

2015-12-07 Thread Deucher, Alexander
> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.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

Re: radeon -Wmaybe-uninitialized crap

2015-12-07 Thread Borislav Petkov
On Mon, Dec 07, 2015 at 04:15:22PM +, Deucher, Alexander wrote: > Odd. Nothing related to these variables has changed in years. Odd indeed. Building that same config on two other boxes doesn't trip those up so it must be something gcc-related on that particular box. Hmmm. --