aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/ScriptInterpreter/Python/PythonDataObjectsTests.cpp
diff options
context:
space:
mode:
authorJuneyoung Lee <aqjune@gmail.com>2020-04-23 08:08:16 +0900
committerJuneyoung Lee <aqjune@gmail.com>2020-04-23 08:08:53 +0900
commitaca335955c0dfe5dc783bf21e1d883c1aae33abc (patch)
tree3ef92bb038becb75eb826a9cac57546a07381fa4 /lldb/unittests/ScriptInterpreter/Python/PythonDataObjectsTests.cpp
parentef9a19cb5c49ce1a7eb6db8ad19230eab17f6feb (diff)
downloadllvm-aca335955c0dfe5dc783bf21e1d883c1aae33abc.zip
llvm-aca335955c0dfe5dc783bf21e1d883c1aae33abc.tar.gz
llvm-aca335955c0dfe5dc783bf21e1d883c1aae33abc.tar.bz2
[ValueTracking] Let analyses assume a value cannot be partially poison
Summary: This is RFC for fixes in poison-related functions of ValueTracking. These functions assume that a value can be poison bitwisely, but the semantics of bitwise poison is not clear at the moment. Allowing a value to have bitwise poison adds complexity to reasoning about correctness of optimizations. This patch makes the analysis functions simply assume that a value is either fully poison or not, which has been used to understand the correctness of a few previous optimizations. The bitwise poison semantics seems to be only used by these functions as well. In terms of implementation, using value-wise poison concept makes existing functions do more precise analysis, which is what this patch contains. Reviewers: spatel, lebedev.ri, jdoerfert, reames, nikic, nlopes, regehr Reviewed By: nikic Subscribers: fhahn, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D78503
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python/PythonDataObjectsTests.cpp')
0 files changed, 0 insertions, 0 deletions