On Fri, Jun 2, 2017 at 2:30 AM, Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: >> .SH OTHER OPTIONS >> .TP >> +.B \-fmemcpy-limit=COUNT >> +By default, sparse will warn if \fBmemcpy()\fR (or \fBmemset()\fR, >> +\fBcopy_from_user()\fR, copy_to_user()\fR) is called with a very large >> +(known at compile-time) byte-count. COUNT is the value under which >> +no such warning will be given. The default limit is 100000. >> +. >> +.TP > > So, in addition to -Wno-memcpy-max-count, you could turn the warning > off with just -fmemcpy-limit=0. cool. > > Thanks! > > ATB, > Ramsay Jones 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. -- 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
