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: LLVM: - the assume intrinsic - scoped noalias metadata - the old JIT being removed - kaleidoscope debug info chapter - TargetMachine/TargetSubtargetInfo API changes - AArch64 FastISel improvements - the new CFL alias analysis - the new vector shuffle lowering - Go bindings - minnum/maxnum intrinsics - statepoint intrinsics Clang: - C++14 support was marked complete - C now defaults to C11 mode - thread-safety analysis was updated - MS ABI compatibility - fpic and -fPIC are now different
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: > > LLVM: > - the assume intrinsic > - scoped noalias metadataHal, could you write something about these?
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: > > LLVM: > - the old JIT being removedLang, do you want to write something about this?
----- Original Message -----> From: "Hans Wennborg" <hans at chromium.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "llvmdev" <llvmdev at cs.uiuc.edu>, "llvm cfe" <cfe-commits at cs.uiuc.edu> > Sent: Wednesday, February 18, 2015 6:35:34 PM > Subject: Re: [3.6 Release] Time to fix the release notes > > 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: > > > > LLVM: > > - the assume intrinsic > > - scoped noalias metadata > > Hal, could you write something about these? >Will do. -Hal -- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory
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: > > LLVM: > - kaleidoscope debug info chapter > - TargetMachine/TargetSubtargetInfo API changesEric, can you add something about these?
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: > > LLVM: > - AArch64 FastISel improvementsChad, do you want to add something about this to the release notes?
Eric Christopher
2015-Feb-19 00:38 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
On Wed Feb 18 2015 at 4:37:24 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: > > > > LLVM: > > - kaleidoscope debug info chapter > > - TargetMachine/TargetSubtargetInfo API changes > > Eric, can you add something about these? >Sure. Though technically I gave a talk on both of them so I could just link to that ;) I'll write something up though. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150219/a51812c1/attachment.html>
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: > > LLVM: > - the new CFL alias analysisIs this hooked up by default? Should we mention it in the notes?
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: > > LLVM: > - the new vector shuffle loweringChandler, will you write something?
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: > > LLVM: > - Go bindingsPeter, do you want to mention this in the release notes?
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: > > LLVM: > - minnum/maxnum intrinsicsMatt, do you want to add this to the release notes?
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: > > LLVM: > - statepoint intrinsicsPhilip, do you want to write something about this for the release notes?
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: > > Clang: > - C++14 support was marked complete > - C now defaults to C11 modeRichard, can you check that the release notes are up to date with this?
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: > > Clang: > - thread-safety analysis was updatedDelesley, is there anything we should add to the release notes for this?
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: > > Clang: > - MS ABI compatibilityReid, I'm sure there's lots of stuff to mention here. I think vectorcall support is new. Do you want to add something about this?
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: > > Clang: > - fpic and -fPIC are now differentJustin, Rafael: should we mention this in the release notes?
(Re-sending to hopefully the correct address. Sorry for the noise.) On Wed, Feb 18, 2015 at 4:38 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: >> >> LLVM: >> - AArch64 FastISel improvements > > Chad, do you want to add something about this to the release notes?
Peter Collingbourne
2015-Feb-19 01:00 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
On Wed, Feb 18, 2015 at 04:41:17PM -0800, Hans Wennborg 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: > > > > LLVM: > > - Go bindings > > Peter, do you want to mention this in the release notes?r229800. -- Peter
Matt Arsenault
2015-Feb-19 01:00 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
> On Feb 18, 2015, at 4:42 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: >> >> LLVM: >> - minnum/maxnum intrinsics > > Matt, do you want to add this to the release notes?Yes, these should be added.
Eric Christopher
2015-Feb-19 01:11 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
Probably best to harass Juergen about it since he did most of them :) -eric On Wed Feb 18 2015 at 5:08:59 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: > > > > LLVM: > > - AArch64 FastISel improvements > > Chad, do you want to add something about this to the release notes? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150219/d08e37c5/attachment.html>
----- Original Message -----> From: "Hans Wennborg" <hans at chromium.org> > To: "george burgess iv" <george.burgess.iv at gmail.com>, "Nick Lewycky" <nicholas at mxc.ca>, "Daniel Berlin" > <dannyb at google.com> > Cc: "llvm cfe" <cfe-commits at cs.uiuc.edu>, "llvmdev" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, February 18, 2015 6:39:17 PM > Subject: Re: [3.6 Release] Time to fix the release notes > > 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: > > > > LLVM: > > - the new CFL alias analysis > > Is this hooked up by default? Should we mention it in the notes?No, not yet. There are still bugs that are being worked out. -Hal> _______________________________________________ > cfe-commits mailing list > cfe-commits at cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory
George Burgess IV
2015-Feb-19 01:33 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
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. :) George> 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: >> >> LLVM: >> - the new CFL alias analysis > > Is this hooked up by default? Should we mention it in the notes?
Rafael Espíndola
2015-Feb-19 16:21 UTC
[LLVMdev] [3.6 Release] Time to fix the release notes
>> Clang: >> - fpic and -fPIC are now different > > Justin, Rafael: should we mention this in the release notes?Probably. What do you guys think of the attached patch? Cheers, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: t.patch Type: application/octet-stream Size: 363 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150219/9b594137/attachment.obj>
On Wed, Feb 18, 2015 at 4:44 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: > > > > Clang: > > - C++14 support was marked complete > > - C now defaults to C11 mode > > Richard, can you check that the release notes are up to date with this? >I think we're all good here. I've added some notes about C11 changes in r229939. C++14 support used to be feature-complete in Clang 3.4. It still is, but it used to too. =) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150219/5c725e12/attachment.html>