@warrenm yeah, the static analyzer cannot track stuff like that
Really starting to think this is a Clang bug: width > 0 height > 0 width * height == 0 https://gist.github.com/warrenm/0021b3fb0e59be8758dd …pic.twitter.com/QCOwQNZ0Uk
-
-
-
@kongtomorrow It’s acting like it’s smart enough to track stuff like that. Agree this is Radar-worthy? -
@warrenm I was looking for a link describing the problem (I could also be remembering). Something like correlated conditionals,@tkremenek? -
@kongtomorrow@warrenm The analyzer tracks both constraints, but can't reason yet about two symbolic values multiplied together. -
@tkremenek Thanks! Any way of avoiding the false flag besides __clang_analyzer__? And if you want a bug report where should I file it?
End of conversation
New conversation -
-
-
@warrenm If width and height are unsigned, they can't be below 0, right? Does it work if the first two conditions use == instead of <=? -
@CastIrony That’s how it was originally. The messages change from “> 0” to “not equal to 0” but otherwise the analysis remains the same.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.