<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 27, 2013, at 7:36 PM, Hal Finkel <<a href="mailto:hfinkel@anl.gov">hfinkel@anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; float: none; display: inline !important;"><span class="Apple-converted-space"> </span>I am not sure that Michael has made a good argument that *this* set of patches is the right approach (aside from saying that it mirrors the interface presented by gcc), but HLE seems like a fairly limited domain and there may not be too many alternatives. I agree that modeling the behavior should allow for additional optimization, and this will be important.</span></blockquote></div><br><div>At the moment there is no concrete plan to add TM specific optimizations. How about implementing HLE support as a set x86-specific intrinsics ? </div></body></html>