JIT: Fix bug in finally cloning caused by unsound callfinally reordering
authorAndy Ayers <andya@microsoft.com>
Wed, 27 Jun 2018 16:49:54 +0000 (09:49 -0700)
committerGitHub <noreply@github.com>
Wed, 27 Jun 2018 16:49:54 +0000 (09:49 -0700)
commitaa00dad99dff3af496b245e6b10500a5e631a8ba
tree1275079defa8f857841f5ed3c537951f06c4ce72
parent373b10e0edf959665d9fdaf312b3dceb8cedbe81
JIT: Fix bug in finally cloning caused by unsound callfinally reordering

Port of #18348 to release/2.1

We need to make sure that if we reorder a callfinally during finally cloning
that the callfinally is actually the one being targeted by the last block in
the try range.

Closes #18332. Linked issue has some more detailed notes.
src/jit/flowgraph.cpp
tests/src/JIT/Regression/JitBlue/GitHub_18332/GitHub_18332.cs [new file with mode: 0644]
tests/src/JIT/Regression/JitBlue/GitHub_18332/GitHub_18332.csproj [new file with mode: 0644]