<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:56.7pt 42.5pt 56.7pt 85.05pt;}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">About CHECK-WORD. There is no problem to return first patch with CHECK-WORD, CHECK-WORD-SAME and etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I added option because there were a lot of opinions that add a lot of new directives is a bad idea.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Elena.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="RU" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="RU" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> mehdi.amini@apple.com [mailto:mehdi.amini@apple.com]
<br>
<b>Sent:</b> Wednesday, August 31, 2016 7:12 PM<br>
<b>To:</b> Vedant Kumar <vsk@apple.com><br>
<b>Cc:</b> Elena Lepilkina <Elena.Lepilkina@synopsys.com>; llvm-dev@lists.llvm.org<br>
<b>Subject:</b> Re: [llvm-dev] RFC: FileCheck Enhancements<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Aug 24, 2016, at 4:46 PM, Vedant Kumar via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
On Aug 24, 2016, at 2:04 AM, Elena Lepilkina <<a href="mailto:Elena.Lepilkina@synopsys.com">Elena.Lepilkina@synopsys.com</a>> wrote:<br>
<br>
Hi all,<br>
<br>
Some discussions and comments were made in reviews. Much time has already passed since last comment and uploading changed patches. I made small summary report about features here, because there are some doubts about syntax of some features and changes in patches
and it'll be great to know more opinions.<br>
<br>
1. FileCheck Enhancement - CHECK-WORD (<a href="https://reviews.llvm.org/D22353">https://reviews.llvm.org/D22353</a>)<br>
I replace special directives by flag --check-word, which turns on mode for each directive in file. It's obvious that this mode can be replaced using \b assert, but current regexp library doesn't have support of this assert and I have no answer to question
about possibility of change current library.<br>
There was the discussion about that such mode can be made default, but there were doubts about necessity of a lot of work for changing existing tests.<br>
And I made experiment which proves that a lot of old tests will be failed with such mode on.<br>
Expected Passes : 15810<br>
Expected Failures : 125<br>
Unsupported Tests : 195<br>
Unexpected Passes : 4<br>
Unexpected Failures: 1128<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
I would rather not introduce churn in our tests by turning on --check-word by<br>
default. I'm also not convinced that turning on --check-word at the test level<br>
is the right move: having a CHECK-WORD directive is more flexible, and not a<br>
serious inconvenience (as compared to writing "CHECK").<br>
<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
2. FileCheck Enhancement - pattern templates (<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22403">https://reviews.llvm.org/D22403</a>)<br>
There are some doubts about syntax of templates. I agree that use of \#, \:, \= is quite different from usual characters in FileCheck and was chosen because of same approach for escaping in regexp. Adrian Prantl suggested to use double-brackets "[[" to escape.<span class="apple-converted-space"> </span><br>
Old syntax:<br>
\#(template_name) - use of template 'template_name'. It can occur in CHECK-PATTERN line, when description of one template includes other templates described before. (Without quote, I don't know how escape # here)<br>
\:(Variable_name)- template variable with name 'variable_name'<br>
\:(variable_name)\=(value) - current value of template variable(it's needed when you use template with variables).<br>
Suggested new syntax:<br>
[[#template_name]] - use of template 'template_name'. It can occur in CHECK-PATTERN line, when description of one template includes other templates described before. (Without quote, I don't know how escape # here)<br>
[[:Variable_name]] - template variable with name 'variable_name'<br>
[[:variable_name=value]] - current value of template variable(it's needed when you use template with variables).<br>
It'll be great to hear more opinions and suggestions about syntax. May be someone has really good ideas. Then I'll be able to change it.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
First, I want to recap the FileCheck workflow Elena is proposing:<br>
<br>
1. Define patterns using the CHECK-DEFINE-PATTERN directive. Defined patterns<br>
have a name and may optionally have parameters.<br>
<br>
2. Use defined patterns in the usual CHECK* directives.<br>
<br>
This is similar to how FileCheck patterns work already. The difference is<br>
that the patterns are defined using a dedicated directive, *not* when the<br>
pattern is first encountered. E.g, here is what you can do today:<br>
<br>
// RUN: echo "%r1 %r2" | FileCheck %s<br>
// CHECK: %[[register:[a-z]+]]1<br>
// CHECK-SAME: %[[register]]2<br>
<br>
With the proposed changes, we'll be able to write something like:<br>
<br>
// RUN: echo "%cmp %cmp" | FileCheck %s<br>
// CHECK-DEFINE-PATERN: register(n): {{[a-z]+}}n<br>
// CHECK: %[[register("1")]]<br>
// CHECK-SAME: %[[register("2")]]</span><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">At first I thought that `register(n)` was some sort of macro, but if it is suppose to be equivalent to the example above of what we do “today”, then using “register(“1”)” is supposed to “capture” the ‘r’ part of the register on the first
match.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So you cannot reuse “register()” later to capture another expression. For instance:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> // RUN: FileCheck %s<br>
// CHECK-DEFINE-PATERN: register(n): {{[a-z]+}}n<br>
// CHECK: %[[register("1")]]<br>
// CHECK-SAME: %[[register("2")]]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> // CHECK: %[[register("1")]]<br>
// CHECK-SAME: %[[register("2")]]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">%r1 %r2<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">%reg1 %reg2 #will fail here.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If true, I find this confusing, if not, I missed something in your example.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">— <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Mehdi<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
I saw "something like" because we haven't decided on the syntax for defining<br>
and using patterns (that's what this thread is for). Briefly, here's the syntax<br>
I'd like to use:<br>
<br>
// Defining patterns.<br>
CHECK-DEFINE-PATERN: <Name>(<Ident>, ...)?: <Pattern><br>
<br>
Where <Pattern> is a list of <PatternElement>, and a <PatternElement> is<br>
either a regex ('{{' POSIX_REGEX '}}') or an argument identifier (IDENT).<br>
<br>
// Using patterns.<br>
CHECK: [[<Name>(<Argument>, ...)?]]<br>
<br>
Fleshing this out some more, here is my candidate grammar (see the end of this<br>
email for the current grammar):<br>
<br>
ACTION <- CHECK ':' MATCH '\n' ;<br>
ACTION <- CHECK-DEFINE-PATTERN ':' IDENT PARAMLIST? ':' PATTERN_ELEMENT* '\n' ;<br>
PARAMLIST <- '(' IDENT (',' IDENT)* ')' ;<br>
PATTERN_ELEMENT <- IDENT ;<br>
PATTERN_ELEMENT <- REGEX ;<br>
MATCH <- ;<br>
MATCH <- TEXT MATCH ;<br>
MATCH <- REGEX MATCH ;<br>
MATCH <- VAR MATCH ;<br>
REGEX <- '{{' POSIX_REGEX '}}' ;<br>
VAR <- '[[' IDENT ':' POSIX_REGEX ']]' ;<br>
VAR <- '[[' IDENT ARGLIST? ']]' ;<br>
ARGLIST <- '(' ARG (',' ARG)* ')' ;<br>
ARG <- "([^"]|\\")*" ;<br>
<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">3. FileCheck Enhancement - repeats in regular expressions (<a href="https://reviews.llvm.org/D22454">https://reviews.llvm.org/D22454</a>), FileCheck Enhancement - Including
files (<a href="https://reviews.llvm.org/D22500">https://reviews.llvm.org/D22500</a>), FileCheck Enhancement - Expressions repeat for CHECK and CHECK-NEXT(<a href="https://reviews.llvm.org/D22501">https://reviews.llvm.org/D22501</a>), FileCheck Enhancement
- CHECK-LABEL-DAG(<a href="https://reviews.llvm.org/D22502">https://reviews.llvm.org/D22502</a>), FileCheck Enhancement - prefixes-regular expressions (<a href="https://reviews.llvm.org/D22503">https://reviews.llvm.org/D22503</a>)<br>
There were no comments about these enhancements at all. Your opinions are very important.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
I personally am waiting for some version of D22403 to land in-tree before<br>
starting on the other reviews. This would help me gauge what others in the<br>
community are thinking and what they need.<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
I hope that some of these changes will be useful for FileCheck users, so I need your opinions to get opportunity for review to be resumed.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
thanks,<br>
vedant<br>
<br>
Original FileCheck grammar (shamelessly copied from the grammar Adrian posted<br>
to D22403):<br>
<br>
ACTION <- CHECK ':' MATCH '\n' ;<br>
MATCH <- ;<br>
MATCH <- TEXT MATCH ;<br>
MATCH <- REGEX MATCH ;<br>
MATCH <- VAR MATCH ;<br>
REGEX <- '{{' POSIX_REGEX '}}' ;<br>
VAR <- '[[' IDENT ':' POSIX_REGEX ']]' ;<br>
VAR <- '[[' IDENT ']]' ;<br>
<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
-----Original Message-----<br>
From: llvm-dev [<a href="mailto:llvm-dev-bounces@lists.llvm.org">mailto:llvm-dev-bounces@lists.llvm.org</a>] On Behalf Of Elena Lepilkina via llvm-dev<br>
Sent: Wednesday, July 20, 2016 4:52 PM<br>
To:<span class="apple-converted-space"> </span><a href="mailto:vsk@apple.com">vsk@apple.com</a><br>
Cc:<span class="apple-converted-space"> </span><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
Subject: Re: [llvm-dev] RFC: FileCheck Enhancements<br>
<br>
List of last patches:<br>
<br>
1. FileCheck Enhancement - CHECK-WORD (llvm-commits was added later as diff update) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22353">https://reviews.llvm.org/D22353</a><span class="apple-converted-space"> </span>2. FileCheck
Enhancement - pattern templates(llvm-commits was added later as diff update) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22403">https://reviews.llvm.org/D22403</a><span class="apple-converted-space"> </span>3. FileCheck
Enhancement - repeats in regular expressions (new review with llvm-commits) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22454">https://reviews.llvm.org/D22454</a><span class="apple-converted-space"> </span>4. FileCheck Enhancement
- Including files (new review with llvm-commits) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22500">https://reviews.llvm.org/D22500</a><br>
5. FileCheck Enhancement - Expressions repeat for CHECK and CHECK-NEXT (new review with llvm-commits) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22501">https://reviews.llvm.org/D22501</a><br>
6. FileCheck Enhancement - CHECK-LABEL-DAG (new review with llvm-commits) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22502">https://reviews.llvm.org/D22502</a><span class="apple-converted-space"> </span>7. FileCheck Enhancement
- prefixes-regular expressions (new review with llvm-commits) -<span class="apple-converted-space"> </span><a href="https://reviews.llvm.org/D22503">https://reviews.llvm.org/D22503</a><br>
<br>
Thanks,<br>
Elena.<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:vsk@apple.com">vsk@apple.com</a> [<a href="mailto:vsk@apple.com">mailto:vsk@apple.com</a>]<br>
Sent: Tuesday, July 19, 2016 8:42 PM<br>
To: Elena Lepilkina <<a href="mailto:Elena.Lepilkina@synopsys.com">Elena.Lepilkina@synopsys.com</a>><br>
Cc: Dean Michael Berris <<a href="mailto:dean.berris@gmail.com">dean.berris@gmail.com</a>>; Mehdi Amini <<a href="mailto:mehdi.amini@apple.com">mehdi.amini@apple.com</a>>;
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
Subject: Re: [llvm-dev] RFC: FileCheck Enhancements<br>
<br>
Hi Elena,<br>
<br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">On Jul 19, 2016, at 6:36 AM, Elena Lepilkina via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br>
<br>
Hi all,<br>
<br>
I made new patches for most of changes with llvm-commits subscriber. But two patches were updated, because there are a lot of comments (patch for CHECK-WORD and patch for templates pattern). Will it be ok?<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
IMO it's fine to keep some of the original reviews if you don't want to discard/recreate their state.<br>
<br>
Please list the most up-to-date set of Phab URL's here, with a little note next to the ones which did not initially CC llvm-commits.<br>
<br>
Thanks again for working on this!<br>
<br>
vedant<br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
Thanks, Elena.<br>
<br>
-----Original Message-----<br>
From: llvm-dev [<a href="mailto:llvm-dev-bounces@lists.llvm.org">mailto:llvm-dev-bounces@lists.llvm.org</a>] On Behalf Of<span class="apple-converted-space"> </span><br>
Dean Michael Berris via llvm-dev<br>
Sent: Tuesday, July 19, 2016 6:53 AM<br>
To: Mehdi Amini <<a href="mailto:mehdi.amini@apple.com">mehdi.amini@apple.com</a>><br>
Cc: via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>><br>
Subject: Re: [llvm-dev] RFC: FileCheck Enhancements<br>
<br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">On 19 Jul 2016, at 04:18, Mehdi Amini via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br>
<br>
We had a long thread about that a few weeks (months?) ago: the conclusion (as I remember) was roughly a guideline to “always start a new revision to have a proper mailing-list thread starting with context (i.e. patch description)”<br>
(and my dissident minority opinion that it is only worth it if there<span class="apple-converted-space"> </span><br>
hasn’t been significant round of reviews going on on the existing<br>
revision)<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
Pardon me for missing that discussion, this may have already been asked before: but is it possible to make arcanist default subscribe the correct commits mailing list in the process? This should make it at least harder to forget.<br>
<br>
Cheers<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>