On Wed, Jun 04, 2014 at 09:19:26AM +0200, Christian Hesse wrote: > > It seems to be related to default gcc flags from distribution? > > Probably. I did compile with optimization, so adding -O2 may do the trick: > > make CFLAGS="${CFLAGS} -O2" all
The warning appears with -O2, so the question is if gcc is not able to reason about the values (ie. a false positive) or if there's a bug that I don't see. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html