similar to: [LLVMdev] Release notes draft done

Please take a look: http://llvm.org/docs/ReleaseNotes.html -Chris -- http://nondot.org/sabre/ http://llvm.org/

> Please take a look: > http://llvm.org/docs/ReleaseNotes.html GCC4.0-based llvm-gcc front-end section: Replace the second "in addition" with something else. "If you can use it, llvm-gcc4 is offers significant new functionality": remove is "In 1.8, it will be removed, replaced with the new SPARC backend." and replaced (no comma) "now have initial

Thanks all, I've incorporated all the feedback so far: http://llvm.org/ChrisLLVM/projects/llvm-www/releases/1.8/docs/ReleaseNotes.html -Chris On Tue, 8 Aug 2006, Bil wrote: > On Aug 8, 2006, at 10:28 AM, Chris Lattner wrote: >> >> Hi All, >> >> Here's the first draft of the LLVM 1.8 release notes. Please take a look >> and send me any comments

misspellings: What's new, 1st paragraph: "nightly tester <http://llvm.org/nightlytest/>, llvm-config enhancEments"; 've found nothing wrong except of it :) On 8/8/06, Chris Lattner <sabre at nondot.org> wrote: > > > Hi All, > > Here's the first draft of the LLVM 1.8 release notes. Please take a look > and send me any comments or feedback you

Hi All, Here's the first draft of the LLVM 1.8 release notes. Please take a look and send me any comments or feedback you have: http://llvm.org/docs/ReleaseNotes.html Thanks! -Chris -- http://nondot.org/sabre/ http://llvm.org/

Chris, Here's my review notes: 1. In the Known problems section you identify PR656 as a known problem. However, this bug is resolved and in January you reported that you verified it on Solaris. So, one of two things needs to happen. Either remove this item from the release notes, or re-open the bug and tell me what still breaks. 2. It seems that several items from the original DRAFT email

Hi All, I am done with my first pass over the release notes, you can see them in mainline here: http://llvm.org/docs/ReleaseNotes.html In addition to the inevitable typos and other things that need to be cleaned up, there are several todo's for specific people: 1. All: please let me know if there is something missing that I forgot. 2. Daniel, please update the clang section [DANIEL]. 3.

Hi All, Here is my current draft of the LLVM 2.1 release announcement. Unlike previous announcements, I'm not planning to largely duplicate the release notes in the announcement. In addition to this, I've checked in the first draft of the release notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ ReleaseNotes.html). I'd really appreciate it if anyone who

>> In addition to this, I've checked in the first draft of the release >> notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ >> ReleaseNotes.html). > > The release notes mention llvm-gcc 4.2, but the prerelease only included > llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both? I will be releasing a source tar ball of llvm-gcc4.2, but

On Aug 8, 2006, at 10:28 AM, Chris Lattner wrote: > > Hi All, > > Here's the first draft of the LLVM 1.8 release notes. Please take > a look and send me any comments or feedback you have: > http://llvm.org/docs/ReleaseNotes.html > Trivial changes: * Most of LLVM is now built with "-pedantic", ensuring better portability to more C++ Compilers. Probably

Hello Chris Tue, 8 Aug 2006 10:28:44 -0700 (PDT) you wrote: > Here's the first draft of the LLVM 1.8 release notes. Please take a > look and send me any comments or feedback you have: > http://llvm.org/docs/ReleaseNotes.html I think list of platforms should include "Intel and AMD machines running on Win32 using MinGW libraries (native)". Or something like this. -- With

Hello ??? I I've created a draft for the Release Notes for CentOS 7.7 at https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7.1908 ??? Manuel

On Friday 21 September 2007, Chris Lattner wrote: > In addition to this, I've checked in the first draft of the release > notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ > ReleaseNotes.html). The release notes mention llvm-gcc 4.2, but the prerelease only included llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both? Bye, Maarten --------------

Hi All, Producing release notes at the end of the release is a becoming more of a problem as the project grows. I've been doing this by going through all of the LLVM commits since the last release and pulling out things that I find interesting and potentially impactful to people. However, as the project grows and there are more commits, this has been becoming less and less practical. To

Chris Lattner wrote: >On Tue, 13 Feb 2007, John T. Criswell wrote: > > >>>>I recommend that you stick with the release_19 branch of both llvm and >>>>llvm-poolalloc. I and others are actively using these branches, so >>>>llvm-poolalloc bug fixes will most likely be made to this branch in >>>>addition to mainline CVS for the forseeable

On Thu, 13 Apr 2006, Reid Spencer wrote: > I just updated again (both llvm and llvm-gcc). The only thing that > changed was: > P test/Regression/CFrontend/2005-12-04-DeclarationLineNumbers.c > > The regression test below was done *with* your llvm-gcc changes to llvm- > expand.c. I don't know what the failures are all about, but I will try > it again. If its the same,

Hi All, The first draft of the llvm 2.2 release notes are now available: http://llvm.org/docs/ReleaseNotes.html The release is scheduled for Monday, so please take a look at them and send me your feedback, or (better yet) just commit fixes directly to the document in llvm/docs/ReleaseNotes.html. In addition to editing improvements I'm particularly interested in adding missing things

Hi Everyone, Here are my notes on the LLVM 1.7 release, which will go into the final release announcement. As Tanya mentioned, it has been far too long since the last release, and there have been a lot of CVS commits since Novemeber. :) I went through them all and pulled out some of the major improvements, which I've listed below. I'm certain that I have forgotten some things, so

Chris Lattner wrote: > Hi All, > > Please review the 2.5 release notes here: http://llvm.org/docs/ReleaseNotes.html > > Let me know if you have any additions, improvements, or see any > oversights. If you have commit access, please just directly change > the document. > > The release is planned to go out in about 24 hours from now! > FYI, I'm reviewing the

On Tue, 13 Feb 2007, John T. Criswell wrote: >>> I recommend that you stick with the release_19 branch of both llvm and >>> llvm-poolalloc. I and others are actively using these branches, so >>> llvm-poolalloc bug fixes will most likely be made to this branch in >>> addition to mainline CVS for the forseeable future. The release_19 >>> branch of