On 26/11/14 19:16, Jan Vesely wrote:
On Wed, 2014-11-26 at 18:47 +, jfons...@vmware.com wrote:
From: José Fonseca
Unfortunately gcc completely ignores the issue, and as result code that
mixes signed/unsigned is so widespread through the code base end up
being little more than noise, potent
On 26/11/14 19:16, Jan Vesely wrote:
> On Wed, 2014-11-26 at 18:47 +, jfons...@vmware.com wrote:
>> From: José Fonseca
>>
>> Unfortunately gcc completely ignores the issue, and as result code that
>> mixes signed/unsigned is so widespread through the code base end up
>> being little more than
Am 26.11.2014 um 19:47 schrieb jfons...@vmware.com:
> From: José Fonseca
>
> Unfortunately gcc completely ignores the issue, and as result code that
> mixes signed/unsigned is so widespread through the code base end up
> being little more than noise, potentially obscuring more pertinent
> warning
On Wed, 2014-11-26 at 18:47 +, jfons...@vmware.com wrote:
> From: José Fonseca
>
> Unfortunately gcc completely ignores the issue, and as result code that
> mixes signed/unsigned is so widespread through the code base end up
> being little more than noise, potentially obscuring more pertinent
From: José Fonseca
Unfortunately gcc completely ignores the issue, and as result code that
mixes signed/unsigned is so widespread through the code base end up
being little more than noise, potentially obscuring more pertinent
warnings.
This change disables them.
---
scons/gallium.py | 1 +
1 fi
