<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 27, 2011, at 12:11 AM, Leo Romanoff wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; 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; "><div><blockquote type="cite">I hope this brief chronicle of the algorithm's inception dispels some of<br></blockquote><blockquote type="cite">its mystery.<br></blockquote><br>Yes. It was very educative! Actually, it would be nice to have a page with a detailed description of the current and may be old register allocator as a part of the LLVM web-site. For starters, the blog entry from Jakob and explanations from this mail thread could be put there. Later it could be extended and improved. What do you think about this idea?<br><br><br>Thanks again,<br> Roman<br></div></span></blockquote></div><br><div>Thanks for your interest. You make several good points and give proper credit to academics who are solving the problem in a more rigorous fashion.</div><div><br></div><div>I'll let Jakob decide how to proceed with the documentation. As I said, the heavy lifting was in the splitter/spiller design, and that could use some explanation.</div><div><br></div><div>-Andy</div></body></html>