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.