Created attachment 367159 [details]
like so

Description of problem:
A memset where both arguments are 0 gets reported with "warning: memset used with constant zero length parameter; this could be due to transposed parameters"

Version-Release number of selected component (if applicable):
glibc-headers-2.10.90-25

How reproducible:
100%

Steps to Reproduce:
1. gcc -O2 -Wall -D_FORTIFY_SOURCE=2 memset(c, 0, 0);
  
Expected results:
No biggy, but with some templated/macroized code there's some circumstances where memset ends up with both args equal to 0, e.g. memset (foo, 0, capacity()). Easy fix in client code too of course, but how about eliding the warning about a 0 len if the other arg is definitely 0