On Thu, May 11, 2017 at 9:41 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Thu, May 11, 2017 at 9:21 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> Conversion to bool is special in C since this conversion >> is essentially the result of the comparison with zero. >> As such, some operations which are normally unsafe to >> do with restricted types, like casting to an unrestricted >> type, are in fact safe to do when converting to bool >> and issuing a warning in those case is useless, confusing >> and causes people to add useless casts in the code in >> order to shut up the warning. >> >> Fix this by catching such 'bool <- restricted type' conversion >> and avoid such warnings. > > The change seems fine. However, have you run the test-suite > with this change? It seems cause some test do not pass. > I assume it is cause by different error message it will output. Oh my, sorry. I *have* run the test-suite but then I've forgotten to commit the change needed for two test cases. Thanks for noticing this. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
