[3.6 Release] Time to fix the release notes
George Burgess IV
george.burgess.iv at gmail.com
Wed Feb 18 17:33:13 PST 2015
You can request that CFLAA is run in opt/clang by passing in a few flags, but it’s not on by default, and there are known correctness issues that we’re currently working through.
Unless anyone feels strongly otherwise, I think it would be best to not add CFLAA until we’re highly confident that it doesn’t give incorrect results. Preferably it would be enabled by default (and/or shown to Make Things Faster™) at the time of mention as well, but correctness comes first. :)
> On Feb 18, 2015, at 7:39 PM, Hans Wennborg <hans at chromium.org> wrote:
> On Wed, Feb 18, 2015 at 4:34 PM, Hans Wennborg <hans at chromium.org> wrote:
>> The 3.6 release is drawing nearer, but the release notes could still
>> use a lot of improvement:
>> LLVM: https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst
>> Clang: https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst
>> The good news is that they can be updated all the way up until
>> release. If you have a patch for the release notes, commit it directly
>> to the branch, or send it to me and I'll commit it for you. It doesn't
>> even have to be a patch proper, just send me some text!
>> I've been going through Alex's excellent weekly news
>> (http://llvmweekly.org) to figure out what changed.
>> Here's a list of things that might be worth mentioning in the notes:
>> - the new CFL alias analysis
> Is this hooked up by default? Should we mention it in the notes?
More information about the cfe-commits