search for: exprn

...} finally { > > try { > > expr4; > > } finally > > … > > } > > } > > } > > } > > } > > > > With duplication, the non-EH path through foo will include each of expr1 > through exprn. The outermost funclet will include (in its non-EH path) > each of expr2 through exprn. The next funclet will include each of expr3 > through exprn. Etc. > > > > Another problem I'd have relying on early inlining is that when the CLR > asks the LLILC Jit to jit one metho...

I think adding transitions to cleanupblocks on the normal execution path would be an optimization barrier. Most passes would see the cleanupblock instruction and run the other way. It's definitely appealing from the perspective of getting the smallest possible code, but I'm OK with having no more than two copies of everything in the finally block. I think with the addition of the