<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/06/2014 11:46 AM, Chandler
Carruth wrote:<br>
</div>
<blockquote
cite="mid:CAGCO0KiS49GL8W7K44H_frF1H-9ij4GZpoC6yjwRVjCv-qGkgw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 6, 2014 at 11:43 AM,
Philip Reames <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:listmail@philipreames.com" target="_blank">listmail@philipreames.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 05/05/2014 03:12 PM, Chandler Carruth
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
3) add some more noisy guidance that textual
attributes should only be used for *target*
attributes, not ones for which IR-optimizers are
semantically aware<br>
</blockquote>
</div>
Point 3 is the only part of this I disagree with. One
important secondary use for string attributes is while
prototyping attributes. Adding a string attributes is
_much_ easier than adding enum ones. I've got several
such string attributes in out of tree branches at the
moment. Most are planned for cleanup and submission (as
full attributes), but being able to prototype them rapidly
was very useful.</blockquote>
</div>
<br>
Oh, sure. Anything experimental seems fine here. But I
wouldn't really expect to start threading such an attribute's
semantics through the trunk optimizer... If there was some
need to keep an attribute clearly marked "experimental" for a
time in trunk until it settled, that also seems not
unreasonable. But I don't think that's the situation we're in
here.</div>
</div>
</blockquote>
Agreed. Just making sure that use case got called out in the
discussion since your writeup didn't acknowledge it. Mission
accomplished. <br>
<br>
Philip<br>
<br>
</body>
</html>