<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 6, 2016 at 3:12 PM, Paul Robinson via llvm-commits <span dir="ltr"><<a href="mailto:llvm-commits@lists.llvm.org" target="_blank">llvm-commits@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">probinson added a comment.<br>
<span class=""><br>
In <a href="http://reviews.llvm.org/D18706#393327" rel="noreferrer" target="_blank">http://reviews.llvm.org/D18706#393327</a>, @probinson wrote:<br>
<br>
> In <a href="http://reviews.llvm.org/D18706#393310" rel="noreferrer" target="_blank">http://reviews.llvm.org/D18706#393310</a>, @dblaikie wrote:<br>
><br>
</span><span class="">> > Would it be better to trigger this directly off the debugger tuning flag<br>
> >  now & drop the specific named flag?<br>
><br>
><br>
> No.  The original discussion over "tuning" specifically concluded that tuning should expand to defaults for feature-specific flags, and never be a controlling condition on its own.  It should always be possible to override a tuning with specific flags.<br>
<br>
<br>
</span>This policy is documented in include/llvm/Target/TargetOptions.h, see the definition of enum DebuggerKind.<br></blockquote><div><br></div><div><br></div><div>Great!</div><div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
<a href="http://reviews.llvm.org/D18706" rel="noreferrer" target="_blank">http://reviews.llvm.org/D18706</a><br>
<br>
<br>
<br>
_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@lists.llvm.org">llvm-commits@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits</a><br>
</div></div></blockquote></div><br></div></div>