diff options
author | Juneyoung Lee <aqjune@gmail.com> | 2020-04-21 00:35:45 +0900 |
---|---|---|
committer | Juneyoung Lee <aqjune@gmail.com> | 2020-04-23 07:57:12 +0900 |
commit | 80faa8c3af856df93faf909f21cdcc397bed068f (patch) | |
tree | 0c93ab4161d3115a84d1149f55a028c89f663f8a /lldb/unittests/ScriptInterpreter/Python/PythonDataObjectsTests.cpp | |
parent | 91ccbe6fdce1766ad62023feded1a1940d06ece7 (diff) | |
download | llvm-80faa8c3af856df93faf909f21cdcc397bed068f.zip llvm-80faa8c3af856df93faf909f21cdcc397bed068f.tar.gz llvm-80faa8c3af856df93faf909f21cdcc397bed068f.tar.bz2 |
RFC: [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