From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> Date: Tue, 23 Apr 2013 08:42:49 -0700 > An explicit cast fixes it, and shows that you were aware of the issue: > > foo &= ~(foo_t)bar; > > and gcc will generate the right logic. Of course, casts then have > their own problems, which your thing avoids (as would just having a > "andn" operation in C) I just want to mention that this is dangerous in different ways, we just recently got a patch in the networking that removed such a cast. The problem is when the cast narrows, f.e.: ~(u8)0 doesn't do what you think it does. That doesn't evaluate to 0xff. You all are very bright and probably know this already. So,if it widens, which is the situation we're talking about, you're good. But until I saw the above u8 thing I never suspected that narrowing in this kind of expression was dangerous. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
