<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Sep 12, 2011, at 11:54 AM, Chandler Carruth 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>Not yet, easy to get though. The overhead is the SmallVector<..., 10> which I use to reverse the VarDecl*s prior to appending them. That *shouldn't* have an observable impact, but I'll measure it. =] I just wanted to see if I was on the right track at all.</div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap: break-word; "><div><div class="im"><br class="Apple-interchange-newline"></div></div></div></blockquote></span></blockquote></div><br><div>I think you are on the right track.</div><div><br></div><div>Keep in mind, that we can also possibly change the internal representation of a CFGBlock if it makes it easier to do the splitting, etc., while still maintaining good performance. For example, we could possibly remove operator[] from CFGBlock, if removing the random access feature makes it easier to implement such changes with good performance.</div></body></html>