<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 04 Jan 2012, at 15:12, Sergei Gorelkin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">However, you can as well try the attached simple patch. It prevents temps referenced from 'finally' blocks from being placed to registers.<br></span></span></blockquote></div><br><div>While I'm not immediately certain how that would be done in the easiest way, it would be best if that were only done for temps that are also used outside the finally block. Temps that are created and destroyed inside the finally block can remain regable without any problems.</div><div><br></div><div><br></div><div>Jonas</div></body></html>