diff options
author | Kristof Umann <dkszelethus@gmail.com> | 2019-03-08 15:47:56 +0000 |
---|---|---|
committer | Kristof Umann <dkszelethus@gmail.com> | 2019-03-08 15:47:56 +0000 |
commit | 2827349c9d7e12fc05e6213c024d50bf59294cb1 (patch) | |
tree | 01378c5f90132543f550f8e906ecc153dbb2a1fd /llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp | |
parent | 8172a0a5f4a8110cc2cb18b1389e9b048946644c (diff) | |
download | bcm5719-llvm-2827349c9d7e12fc05e6213c024d50bf59294cb1.tar.gz bcm5719-llvm-2827349c9d7e12fc05e6213c024d50bf59294cb1.zip |
[analyzer] Use the new infrastructure of expressing taint propagation, NFC
In D55734, we implemented a far more general way of describing taint propagation
rules for functions, like being able to specify an unlimited amount of
source and destination parameters. Previously, we didn't have a particularly
elegant way of expressing the propagation rules for functions that always return
(either through an out-param or return value) a tainted value. In this patch,
we model these functions similarly to other ones, by assigning them a
TaintPropagationRule that describes that they "create a tainted value out of
nothing".
The socket C function is somewhat special, because for certain parameters (for
example, if we supply localhost as parameter), none of the out-params should
be tainted. For this, we added a general solution of being able to specify
custom taint propagation rules through function pointers.
Patch by Gábor Borsik!
Differential Revision: https://reviews.llvm.org/D59055
llvm-svn: 355703
Diffstat (limited to 'llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions