summaryrefslogtreecommitdiffstats
path: root/clang-tools-extra/clang-tidy/bugprone/SuspiciousMemsetUsageCheck.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Update the file headers across all of the LLVM projects in the monorepoChandler Carruth2019-01-191-4/+3
| | | | | | | | | | | | | | | | | to reflect the new license. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351636
* Re-commit r347419 "Update call to EvaluateAsInt() to the new syntax."Hans Wennborg2018-11-281-8/+15
| | | | llvm-svn: 347757
* Revert r347419 "Update call to EvaluateAsInt() to the new syntax."Hans Wennborg2018-11-271-15/+8
| | | | | | It's pre-requisite was reverted in r347656. llvm-svn: 347657
* Update call to EvaluateAsInt() to the new syntax.Bill Wendling2018-11-211-8/+15
| | | | llvm-svn: 347419
* Revert 347366, its prerequisite 347364 got reverted.Nico Weber2018-11-211-15/+8
| | | | llvm-svn: 347390
* Update EvaluateAsInt to the new syntax.Bill Wendling2018-11-201-8/+15
| | | | llvm-svn: 347366
* Port getLocStart -> getBeginLocStephen Kelly2018-08-091-3/+3
| | | | | | | | | | Reviewers: javed.absar Subscribers: nemanjai, kbarton, ilya-biryukov, ioeric, jkorous, arphaman, jfb, cfe-commits Differential Revision: https://reviews.llvm.org/D50354 llvm-svn: 339400
* [clang-tidy] Add bugprone-suspicious-memset-usage checkGabor Horvath2017-07-141-0/+127
Created new module bugprone and placed the check in that. Finds memset() calls with potential mistakes in their arguments. Replaces and extends the existing google-runtime-memset-zero-length check. Cases covered: * Fill value is a character '0'. Integer 0 might have been intended. * Fill value is out of char range and gets truncated. * Byte count is zero. Potentially swapped with the fill value argument. Patch by: Reka Nikolett Kovacs Differential Revision: https://reviews.llvm.org/D32700 llvm-svn: 308020
OpenPOWER on IntegriCloud