<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; "><div><div>On Sep 18, 2013, at 4:54 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 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 dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Andy, this really feels like a hack, and a bad hack at that.</div><div><br></div><div>Where is the requirement for the core library to have no static initializers coming from? What is the support plan here? What problem are you actually trying to fix?</div>
</div></div></div></blockquote><div><br></div><div>Just for clarity, I have read the llvmdev thread, and I understand the *general* goal, but this patch itself doesn't seem like a clean incremental step toward that goal, doesn't reference any of the constructs under discussion in that thread.</div></div></div></div></blockquote><div><br></div>I totally agree. This seems like a hack that would be resolved by making cl::opt's get compiled out in non-assert builds, which you already described.</div><div><br></div><div>-Chris</div><div><br></div></body></html>