diff options
| author | Alexander Kornienko <alexfh@google.com> | 2016-01-11 10:26:29 +0000 |
|---|---|---|
| committer | Alexander Kornienko <alexfh@google.com> | 2016-01-11 10:26:29 +0000 |
| commit | dcbe5a9d1727fc83b9263fe8d70e534377f33d4a (patch) | |
| tree | 9c1c2417594499fd0e642e056cf551e74e29d358 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h | |
| parent | d0f89cd721df6943e36e4bbd9715317b08b7f578 (diff) | |
| download | llvm-dcbe5a9d1727fc83b9263fe8d70e534377f33d4a.zip llvm-dcbe5a9d1727fc83b9263fe8d70e534377f33d4a.tar.gz llvm-dcbe5a9d1727fc83b9263fe8d70e534377f33d4a.tar.bz2 | |
[clang-tidy] Fix a false positive in google-runtime-memset
google-runtime-memset no longer issues a warning if the fill char value
is known to be an invalid fill char count.
Namely, it no longer warns for these:
memset(p, 0, 0);
memset(p, -1, 0);
In both cases, swapping the last two args would either be useless (there is
no actual bug) or wrong (it would introduce a bug).
Patch by Matt Armstrong!
llvm-svn: 257320
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions