3.7.1 Release Update - Stable patches deadeline extended to November 9 - testers needed

Hi,

I know a lot of people were busy with the dev-meeting last week, so I've
decided to continue to accept stable patches until November 9. I
would still like to keep the original schedule of an -rc1 release on
November 10, so if there are any newly submitted patches that take
more than a few days to get approved, they will probably end up
going into llvm 3.7.2.

I am currently working through my list of candidate stable patches to make
sure everything is getting approved / merged. If you think I may have
forgotten about your patch, please ping the thread or the audit on phabricator.

As always we need testers for the releases, so if you are interested
in doing testing, let me know.

Thanks,
Tom

Can test for Ubuntu 14.04 and 15.10 x86_64.

Ben

Can test for Windows x64.

Hi Tom,

I have a patch, r249165, which fixed PR21695 and also fixes PR20025.

It's small and self contained. Shall I apply?

cheers,
--renato

Happy to build and test for Windows as usual.

Cheers,
Hans

Hi Tom,

I will do the testing for FreeBSD, as usual.

-Dimitry

Hi Tom,

I have a patch, r249165, which fixed PR21695 and also fixes PR20025.

We just need Tim's approval. I have opened an audit for this:

http://reviews.llvm.org/rL249165

-Tom

Count me in for OS X testing.

Cheers,
Sebastian

As always we need testers for the releases, so if you are interested
in doing testing, let me know.

I'll test MIPS as usual.

I want to help testing this release. I work for Facebook and can test cfe on our backends codebase.
Should I use release_37 branch for this? Where can I find what work is still in progress for this release?

Thanks,
Igor

Tom,

In anticipation of 3.7.1 I tried to build a release of 3.7.0 against SuSE Linux Enterprise 11.3. Some of the test suite fails to compile. It looks like it requires features not yet availabke in that distro. Is there a minimum supported glibc version?

Assuming there is and it’s newer than what’s available, could I instead build the release tarball against musl?

I’ll do Fedora and openSUSE as usual.

Tom, I tried building 3.7.0 for SuSE Linux Enterprise 11SP3. It failed to build some specific test cases for lack of specific (new) pthread function declarations. Assuming the problem is that the glibc is too old to be supported by clang/llvm, can I build a 3.7.1 release against musl instead?

Was Suse's 3.7.0 built against Musl?

--renato

No, there is no tarball for SUSE Enterprise Linux 11, I’ve offered to build one. My clang builds have worked really well for me but it’s mildly tricky to build for this old platform. But this is my first time trying the test-release.sh process.

Oh, I see. CMake should make sure you have new enough libraries.

If that version of Suse doesn't have minimal versions, and we never
had Suse 11 binaries before, and musl fits the bill, I can't see why
not.

Tom, ideas?

cheers,
--renato