<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 16, 2014 at 9:48 AM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span> wrote:<br><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">
Author: alp<br>
Date: Wed Jul 16 11:48:33 2014<br>
New Revision: 213171<br>
<br>
URL: <a href="http://llvm.org/viewvc/llvm-project?rev=213171&view=rev" target="_blank">http://llvm.org/viewvc/llvm-project?rev=213171&view=rev</a><br>
Log:<br>
Make clang's rewrite engine a core feature<br>
<br>
The rewrite facility's footprint is small so it's not worth going to these<br>
lengths to support disabling at configure time, particularly since key compiler<br>
features now depend on it.<br>
<br>
Meanwhile the Objective-C rewriters have been moved under the<br>
ENABLE_CLANG_ARCMT umbrella for now as they're comparatively heavy and still<br>
potentially worth excluding from lightweight builds.<br>
<br>
Tests are now passing with any combination of feature flags. The flags<br>
historically haven't been tested by LLVM's build servers so caveat emptor.</blockquote><div><br></div><div>Hi Alp,</div><div><br></div><div>A reorganization of this magnitude should be discussed before being committed. More generally, changes to the file organization should generally get the nod of approval from the relevant code owner. (That said, I think this reorg is an improvement, so I'm not objecting to the change, just to the process.)</div>
<div><br></div><div>It also would have been courteous to ask if anyone was using theĀ <span style="font-family:arial,sans-serif;font-size:13px">CLANG_ENABLE_REWRITER flag before removing it. SeeĀ </span><font face="arial, sans-serif">r170135, which gives a justification for including this flag, which doesn't seem to have gone away.</font></div>
<div><br></div><div>Thanks!</div></div></div></div>