[PATCH] Fix GLIBC build error with recent GCC6

[Florian Weimer]

On 07/20/2015 07:46 PM, Jeff Law wrote:

> Extra credit if you can file a bug report upstream for GCC.

<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946>

> This kind of false positive often leads to discovery of cases that GCC
> is not optimizing as well as it should.  Killing the false positive and
> generating better code in the process is obviously a good thing.

What's particularly worrying is that the warning says “is”, not ”may
be”.  Doesn't this indicate the GCC miscompiles some paths?

-- 
Florian Weimer / Red Hat Product Security