<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<div class="moz-cite-prefix">On 06/30/2017 09:01 PM, C Bergström via
cfe-dev wrote:<br>
</div>
<blockquote
cite="mid:CAOnawYrPLxyNv8fS6VgeOB-SmK3qHEteRB5yXUJaB2q0puV4ZA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>I don't know how others feel, but it seems this was removed
more by feeling and less by actual data points. It doesn't
mean it wasn't the correct choice, but just because nobody
spoke up could mean that they silently enjoy the benefits and
maybe some end user far away isn't subscribed. With this in
mind - I hope others would consider turning optimizations into
an Assert, Warning or Error if they will be removed - at least
for a release. </div>
</div>
</blockquote>
<br>
They'll get a warning about an unused command-line argument. Also, I
think there's been some discussion about adding a more-specific
warning for this case.<br>
<br>
Thanks again,<br>
Hal<br>
<br>
<blockquote
cite="mid:CAOnawYrPLxyNv8fS6VgeOB-SmK3qHEteRB5yXUJaB2q0puV4ZA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>That way there's some visible warning that users had a
chance to see and potentially relay the feedback. The middle
ground could be disabling the transformation and just warning
on the analysis pass. "Foo optimization has been removed and
it may impact your code performance"...<br>
<br>
</div>
Too much work?<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Jul 1, 2017 at 9:32 AM,
Chandler Carruth via cfe-dev <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@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">
<div dir="ltr">Already added in the commit (I think)</div>
<div class="HOEnZb">
<div class="h5"><br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Jun 30, 2017 at 3:58 PM Hans
Wennborg <<a moz-do-not-send="true"
href="mailto:hans@chromium.org" target="_blank">hans@chromium.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
Thu, Jun 29, 2017 at 3:42 PM, Chandler Carruth via
cfe-dev<br>
<<a moz-do-not-send="true"
href="mailto:cfe-dev@lists.llvm.org"
target="_blank">cfe-dev@lists.llvm.org</a>>
wrote:<br>
> If you don't use BBVectorize at all, you can
ignore this.<br>
><br>
> Hal suggested this in a thread in 2014:<br>
> <a moz-do-not-send="true"
href="http://lists.llvm.org/pipermail/llvm-dev/2014-November/079091.html"
rel="noreferrer" target="_blank">http://lists.llvm.org/<wbr>pipermail/llvm-dev/2014-<wbr>November/079091.html</a><br>
><br>
> None objected then, and I don't think any new
uses have arisen so I plan to<br>
> just remove it. It is causing maintenance
burden, complexity, and is a set<br>
> of features I'd rather not port to the new PM.<br>
><br>
> Just an FYI email to folks so they aren't
confused when the patches land.<br>
<br>
Maybe worth mentioning in the release notes?<br>
</blockquote>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
cfe-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a moz-do-not-send="true"
href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev"
rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
</body>
</html>