Alexey Andreev 8f68c64193 Fix bug in repeated field read elimination. ... There's a case that was missing in this optimization. We install invalidation points on a block's dominance frontiers when the block contains som invalidation instructions. However, if a block is an entry to exception handler, state is always invalidated. This should be done since exception handler may recover and proceed with some code that follows try/catch block. Without this change code after try/catch inherits state of `try` block, which is invalid, since `catch` is another source from where we can get there. We can't rely on regular instruction analysis in `catch` blocks, since we get into `catch` from an unpredictable point.		2020-05-18 17:24:21 +03:00
..
src	Fix bug in repeated field read elimination.	2020-05-18 17:24:21 +03:00
pom.xml	Update version to 0.7.0	2019-09-24 16:26:14 +03:00