<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello everyone,<br>
<br>
If you've read through my previous introduction email
(<a class="moz-txt-link-freetext" href="http://lists.llvm.org/pipermail/llvm-dev/2016-May/099573.html">http://lists.llvm.org/pipermail/llvm-dev/2016-May/099573.html</a>), you
can safely ignore this message.<br>
<br>
The short story is: CFL-AA does not seem to be broken anymore.
Please try it out and help us find more bugs / performance issues if
switching to it in the future sounds interesting to you.<br>
<br>
Here are more backgrounds: I was working on a GSoC project, whose
first step is to fix cfl-aa. After a bug was patched up in r268269,
bootstrapping llvm+clang with standalone cfl-aa as well as
cfl-aa+basicaa breaks nothing in llvm test-suite. It shows that
cfl-aa is in a pretty good shape today and are almost ready to be
turned out by default. But before we can do this, we'd like to
gather enough evidences that it is a safe move. A more thorough
description of the current status can be found in the link provided
at the beginning of this message.<br>
<br>
To compile your codes with cfl-aa turned on, simply add "
<meta http-equiv="content-type" content="text/html; charset=utf-8">
-mllvm -use-cfl-aa -mllvm -use-cfl-aa-in-codegen" option to the
clang command line arguments. <br>
<pre class="moz-signature" cols="72">--
Best Regards,
--
Jia Chen
</pre>
</body>
</html>