diff options
| author | Artem Dergachev <artem.dergachev@gmail.com> | 2019-04-26 02:05:18 +0000 |
|---|---|---|
| committer | Artem Dergachev <artem.dergachev@gmail.com> | 2019-04-26 02:05:18 +0000 |
| commit | 48e7a2fa8cf072749b8f7b1baa7aaa38e710b68d (patch) | |
| tree | 1ff080ed2c5fa6a0afe74b36062a975cf26474e7 /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | e264ac6ae19a5dfce26582c7240df402cba269ad (diff) | |
| download | llvm-48e7a2fa8cf072749b8f7b1baa7aaa38e710b68d.zip llvm-48e7a2fa8cf072749b8f7b1baa7aaa38e710b68d.tar.gz llvm-48e7a2fa8cf072749b8f7b1baa7aaa38e710b68d.tar.bz2 | |
[analyzer] RetainCount: Add a suppression for "the Matching rule".
In the OSObject universe there appears to be another slightly popular contract,
apart from "create" and "get", which is "matching". It optionally consumes
a "table" parameter and if a table is passed, it fills in the table and
returns it at +0; otherwise, it creates a new table, fills it in and
returns it at +1.
For now suppress false positives by doing a conservative escape on all functions
that end with "Matching", which is the naming convention that seems to be
followed by all such methods.
Differential Revision: https://reviews.llvm.org/D61161
llvm-svn: 359264
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions
