code optimized away before a deopt

[Deneau, Tom]

I've noticed that if I have a snippet that does a test and if the test fails, branches to a block that does some cleanup operations and then calls DeoptimizeNode.deopt(xxx, yyy), the cleanup code  gets "optimized away".  I guess this is related to what Gilles was talking about, maybe the cleanup operations were considered not state changing?

In our current state of HSAIL backend, a deopt just returns early from the kernel.   Is there something I can do to make the cleanup code get emitted before the deopt?

-- Tom