llvm-project/llvm/test/Feature/OperandBundles
Philip Reames 43907d608a 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.
2022-01-18 12:34:18 -08:00
..
adce.ll [test] Use -passes syntax in Feature/OperandBundles lit tests 2021-11-27 09:52:55 +01:00
basic-aa-argmemonly.ll [test] Use -passes syntax in Feature/OperandBundles lit tests 2021-11-27 09:52:55 +01:00
dse.ll [test] Use -passes syntax in Feature/OperandBundles lit tests 2021-11-27 09:52:55 +01:00
early-cse.ll Autogen a test for ease of update 2022-01-18 12:08:13 -08:00
function-attrs.ll Fix incorrect inference of writeonly despite reading operand bundle 2022-01-18 12:34:18 -08:00
inliner-conservative.ll
merge-func.ll
pr26510.ll [funcattrs] Fix a bug in recently introduced writeonly argument inference 2021-12-03 08:57:15 -08:00
special-state.ll