diff options
| author | Philip Reames <listmail@philipreames.com> | 2022-01-18 12:08:40 -0800 |
|---|---|---|
| committer | Philip Reames <listmail@philipreames.com> | 2022-01-18 12:34:18 -0800 |
| commit | 43907d608a22a61245813efeb978928fdfb90b6a (patch) | |
| tree | a65fd3a649b474009213589284165352561f9509 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h | |
| parent | d3b756c51c1b42f653b8abf2b2e83a2321befb9d (diff) | |
| download | llvm-43907d608a22a61245813efeb978928fdfb90b6a.zip llvm-43907d608a22a61245813efeb978928fdfb90b6a.tar.gz llvm-43907d608a22a61245813efeb978928fdfb90b6a.tar.bz2 | |
Fix incorrect inference of writeonly despite reading operand bundle
If we have a writeonly function called from a callsite with a potentially reading operand bundle, we can not conclude the callsite is writeonly.
The changed test is the only one I've been able to demonstrate a current miscompile on, but an incorrect result here could show up in a bunch of subtle ways. For instance, this issue caused several spurious test changes when combined with D117591.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h')
0 files changed, 0 insertions, 0 deletions