LLVM 3.0rc1 Testing Begins!

Hi all,

Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here:

http://llvm.org/pre-releases/3.0/

A Word About Patches

I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must be approved by the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners). Please CC me on all emails for patches you want in. I may not catch them otherwise.

Code owners, please be stringent about which patches you accept. Please approve only those patches that are critical for the release. I’m no longer accepting new features into 3.0. I will accept patches for features which were turned on before the 3.0 branch, if they are absolutely necessary and have gone through at least one nightly test run on ToT.

Share and enjoy!
-bw

Bill,

Although it shouldn't be a roadblock to seasoned testers, I note that in the llvm tarball, tools/clang is a symlink to

  /Volumes/Sandbox/llvm/3.0-release/rc1/cfe.src

whereas it should probably be a symlink to clang-3.0rc1 since that's what the clang tarball unpacks to.

In general, if you want a wider audience than folks who regularly build from Subversion to build it, it would probably be a good idea to stick a README in http://llvm.org/pre-releases/3.0/ telling people how to build it.

Also, do we want people to be testing libc++ too? Likewise lldb?

    M.E.O.

Hi Bill,

Do we have a list of which PRs have been filed that are considered release blockers?

-Jim

Have you a command line to do an anonymous Subversion checkout of the
3.0rc1 tag?

Or should I just stick with the official tarball?

Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :slight_smile: Any that are regressions should be marked with the 'regression' keyword and be a release blocker.

-bw

The official tarball is the same, but you can get the 3.0rc1 tag from here:

  http://llvm.org/svn/llvm-project/$proj/tags/RELEASE_30/rc1

where $proj is replaced by the appropriate project name in SVN (llvm, cfe, dragonegg, etc.).

-bw

Hi;

imho http://llvm.org/bugs/show_bug.cgi?id=9614 should be a release blocker.

Regards.

Bill,

Although it shouldn't be a roadblock to seasoned testers, I note that in the llvm tarball, tools/clang is a symlink to

  /Volumes/Sandbox/llvm/3.0-release/rc1/cfe.src

whereas it should probably be a symlink to clang-3.0rc1 since that's what the clang tarball unpacks to.

In general, if you want a wider audience than folks who regularly build from Subversion to build it, it would probably be a good idea to stick a README in http://llvm.org/pre-releases/3.0/ telling people how to build it.

Good point. I'll fix this for phase 2 testing.

Also, do we want people to be testing libc++ too?

I considered doing a libc++ release, but it's too late in the release timeframe to get started doing this. We don't have a methodology on how to verify libc++, etc. I'll come up with something for 3.1 and beyond.

Likewise lldb?

Ditto. :slight_smile:

-bw