On Fri, Jun 2, 2017 at 3:42 AM, Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: >> Well, for now setting the limit to 0 would just warn about any >> non-zero memcpy/memset >> but it's something that could very easily be added, sure. > > Yes, as I noted in another email, I didn't read the code correctly! > (and in my patch I had a single -Wmem-limit=n argument which _did_ > disable the check when n = 0). > > Naming issues aside (and I'm bad at naming, so don't listen to me > on that), I like your -W[no-]memcpy-max-count and -fmemcpy-limit=n > split. > > [You may want to remove the '=COUNT' from the commit message of > the 2/3 patch]. Oh yes, indeed. Thanks. -- 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
