| commit | e8b1420668c77972720445d4fa0efd8e3ff37b9c | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 21 Nov 2011 07:06:15 +0000 (21 10:06 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 21 Nov 2011 07:06:15 +0000 (21 10:06 +0300) | ||
| tree | 8fdde27d7cc2c429fdd290868909b1454242df3b | treesnapshot (tar.gz zip) |
| parent | 212f4baff1af1638344545d8a164bc273af1a52f | commitdiff |
extra: unops don't normally change the value of a variable
The only unops that I can think of which change the value of a variable
are ++ and -- as in x++ means x changed. The old code said that everything
changed so if you had somthing like: "if (&a == &b);" then that reset
the values of a and b. That broke the min() and max() macros.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The only unops that I can think of which change the value of a variable
are ++ and -- as in x++ means x changed. The old code said that everything
changed so if you had somthing like: "if (&a == &b);" then that reset
the values of a and b. That broke the min() and max() macros.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_extra.c | diffblobblamehistory |