<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 2, 2015, at 1:17 PM, Hal Finkel <<a href="mailto:hfinkel@anl.gov" class="">hfinkel@anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><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-stroke-width: 0px; float: none; display: inline !important;" class="">I should add that I'm somewhat afraid, however, of the compile-time implications of adding the necessary hook.</span></div></blockquote>I was just going to say this myself.</div><div><br class=""></div><div>In fact, even if you don’t add a hook for tracking new values, just using value handles in AA could prove to be expensive. </div><div><br class=""></div><div>A typical optimized piece of code has more load instructions than binary instructions. If you only cached loads with value handles, you’re already creating a huge number of handles, and these are currently entries in a map (pImpl->ValueHandles[V] if you’re curious).</div><div><br class=""></div><div>TL;DR: If we are going to create this many value handles, we should strongly consider finding a way to represent them more cheaply.</div><div><br class=""></div><div>Cheers,</div><div>Pete</div><br class=""></body></html>