Am 26.11.2014 um 19:47 schrieb jfons...@vmware.com: > From: José Fonseca <jfons...@vmware.com> > > 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 file changed, 1 insertion(+) > > diff --git a/scons/gallium.py b/scons/gallium.py > index 8e2090b..d9bf760 100755 > --- a/scons/gallium.py > +++ b/scons/gallium.py > @@ -462,6 +462,7 @@ def generate(env): > ] > ccflags += [ > '/W3', # warning level > + '/wd4018', # signed/unsigned mismatch > '/wd4244', # conversion from 'type1' to 'type2', possible loss > of data > '/wd4305', # truncation from 'type1' to 'type2' > '/wd4800', # forcing value to bool 'true' or 'false' > (performance warning) >
I'm pretty sure I've seen gcc warnings about unsigned/signed mismatches too, there's some options for that. I don't know though if they apply to exactly the same situations. Either way if they are annoying disabling them is fine by me, they _usually_ don't tend to be harmful bugs... Roland _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
