On Sat, Feb 10, 2018 at 11:00:26AM -0800, Christopher Li wrote: > On Wed, Jan 31, 2018 at 2:40 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > This warning is issued when trying to linearize a call > > expressions with a null expr->ctype but such null ctype > > is a consequence of an error detected during evaluation > > and this error must already have issued a warning or an > > error message specific to the problem. > > > > In short, this "call with no type" is non-informative > > and redundant, so avoid usless noise and remove this > > warning. > > The change looks fine to me. This the change assume the > expr->ctype be NULL is result of an error and has been reported > before. I am sure that assumption holds for most of the cases. Not > sure it holds for all corner cases. I consider that if it this not the case, it's a bug which will need to be fixed by adding the proper error reporting. But I haven't yet seen such case. -- 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
