<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/16/13 9:08 AM, James Molloy
wrote:<br>
</div>
<blockquote cite="mid:000001cefa81$7d3c92d0$77b5b870$@arm.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1"><o:p></o:p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So the version attached reads metadata
attached to CallInsts. The schema for the metadata is detailed
in the proposed LangRef addition, but basically it describes a
list of potential vectorization candidates. Each candidate has
a vector width, a llvm::Function* (or MDString) giving the
target function and a string describing how the function
arguments need to be handled.</p>
</div>
</blockquote>
Specifically with regards to metadata, why is the metadata on the
call site not the function declaration? I would expect that a call
to "cos" would always vectorize to the same "cos4". Is supporting
different vectorizations at different points of the program a key
goal?<br>
<br>
Ignoring most of the discussion since it seems like a good
conclusion has been reached.<br>
<br>
Yours,<br>
Philip Reames<br>
</body>
</html>